Hostinger AI Prompts for Portfolio Websites: Copy-Paste Templates You Can Use

Jonas is a freelance UX designer with five years of experience and three projects he is proud of: a booking flow for a regional ferry operator, a redesign of a charity's donation form, and a design system for a small health-tech start-up. His portfolio is a PDF. Recruiters ask for a link. He has one weekend and a Hostinger account, and he wants a site that looks considered rather than templated.

This guide gives copy-paste Hostinger AI prompts for portfolio websites, each filled in with realistic detail so you can see what a good brief looks like. It is for designers, developers, photographers, writers and students building a personal portfolio on a hosting platform's AI tools. Hostinger's AI website builder and related tools change over time, so check the current features, limits, templates and pricing. The approach works whether you type prompts into the builder's description box, an AI writing assistant, or both: brief the structure and the copy separately, then edit by hand.

What AI does well here, and where you must step in

Good at

• Turning a clear brief into a page structure, section order and first-draft copy.
• Producing consistent microcopy: button labels, navigation, form messages.
• Suggesting SEO titles, descriptions and image alt text from your real content.

Needs you

• Case studies need your real process, decisions and results. Never let the tool invent projects, clients, awards, testimonials or metrics. If a number is not in your records, leave it out.
• Client work may be under a confidentiality agreement; get permission before showing it and blur or omit sensitive details.
• Generic AI layouts often look alike. Your photos, your writing and your point of view are what make a portfolio memorable.
• Check performance, accessibility, privacy and contact-form spam protection before launch.

A formula for portfolio prompts

Who you are + who will read it + the goal of the site + page list + tone + real content you will supply + constraints (colour, fonts, accessibility) + what to avoid. Always say who the visitor is (a hiring manager skimming for 90 seconds is different from a client commissioning a brand).

Plan the site

The site brief

Write a website brief for a personal portfolio. Owner: Jonas, a freelance UX designer (5 years) who designs booking, payment and form flows for service organisations. Visitors: hiring managers and small-business owners who will skim for under two minutes on a laptop or phone. Goal: get a call booked. Pages: Home, 3 case studies, About, Contact. Tone: plain, thoughtful, a little dry; no buzzwords. Visual direction: lots of whitespace, one accent colour (deep teal), a readable serif for headings and a clean sans for body text, AA contrast. Output: a sitemap, the job of each page in one sentence, the primary call to action per page, and a list of content I must supply before building. Do not invent any projects, clients or results.

Why it works: It states visitor behaviour and a single goal, so every page has a job. What to expect / check: A realistic content checklist (screenshots, process notes, permissions). Failure: made-up client names; delete them. Iterate: "Cut the sitemap to the minimum for a first launch and list what can wait until month two."

Prompt to feed the builder

Create a portfolio website for a freelance UX designer named Jonas. Sections on the home page: hero with a one-sentence value statement and a "See my work" button, three featured case study cards with a title, one-line summary and image placeholder, a short about strip with a photo placeholder, and a contact strip with an email button. Style: minimal, generous whitespace, teal accent (#0E6B6B), serif headings, sans-serif body, accessible contrast, mobile-first. Use placeholder text only where I have not provided content, and mark every placeholder in square brackets so I can replace it. Do not add testimonials, logos or statistics.

Why it works: Marking placeholders in brackets keeps invented content from slipping into the live site. What to expect / check: Structure and style right on the first pass; copy will be generic. Replace placeholders before publishing. Iterate: "Move the contact strip into a sticky header button and reduce the hero height so the first case study is visible on a phone without scrolling."

Write the content

Case study structure from your notes

Turn my project notes into a 450-word case study draft in first person. Project: booking flow redesign for a regional ferry operator. Notes: I was the only designer; 8-week engagement; the problem was customers abandoning bookings at the passenger-details step; I ran 6 usability sessions with 6 participants; I removed 4 optional fields and added inline error messages; developers shipped it in sprint 5; the operator told me completion improved but I do not have the exact figure. Structure: Context, Problem, My role, What I did, Outcome, What I would do differently. Rules: do not state any number I have not given you; for the outcome, describe it honestly without a figure; keep sentences short; no filler like "innovative" or "seamless". Mark any sentence where you made an assumption with [CHECK].

Why it works: The notes define what the model may say, and "no exact figure" is stated rather than papered over. What to expect / check: Honest outcome wording. Failure: invented percentages; remove them. Iterate: "Rewrite the Problem section in under 80 words and open with the user's frustration, not the business metric."

Case study headline and summary variants

Give me 5 headline-and-summary options for the case study card on my home page. Project: redesign of a charity's online donation form. Facts: 3-week project, I worked with one developer, reduced the form from 3 pages to 1 and added a clear "monthly or one-off" choice, tested with 5 volunteers. Each headline max 8 words, each summary max 20 words, no hype, no unproven claims, written for a hiring manager. Output as a table with a column noting which one leads with the problem, which with the outcome, and which with my role.

Why it works: Constraints on length and type of lead let you choose an angle on purpose. What to expect / check: Differences in angle, not just wording. Iterate: "Make option 3 sound less formal and keep it under 16 words."

About page that sounds like a person

Write a 180-word About page for Jonas, a UX designer. Facts: started in a customer-support role, which taught me how people actually fail with forms; moved into design five years ago; I work with service organisations such as transport and charities; I like clear writing and plain language; outside work I swim and repair old bicycles. Voice: warm, direct, first person. Include one concrete sentence on how I work with clients (I start by watching real users) and a closing line inviting a short call. Avoid: "passionate", "rockstar", "ninja", a list of buzzwords, and anything not in the facts.

Why it works: Personal facts and a concrete work habit differentiate the page. What to expect / check: No invented biography. Read aloud; it should sound like you. Iterate: "Cut it to 90 words for a mobile-first version."

Microcopy and contact form

Write microcopy for a portfolio contact form: heading, short intro (max 25 words), field labels (name, email, project type with 4 options, message), placeholder text, a success message, an error message for invalid email, and a short privacy note saying how the message will be used. Tone: friendly, plain. Also suggest a spam-protection approach (for example a hidden honeypot field or the platform's built-in options) and remind me to check the current privacy and consent rules that apply in my country. Do not make legal claims.

Why it works: Microcopy and spam protection are usually forgotten until a problem happens. What to expect / check: Clear, short strings. Test the form yourself before launch. Iterate: "Add a reply-time expectation that I can honestly meet, for example two working days."

Polish and launch

SEO titles, descriptions and alt text

Create SEO metadata for my portfolio pages. Pages: Home, Ferry Booking Flow case study, Charity Donation Form case study, About, Contact. For each: a title tag (max 60 characters), a meta description (140-155 characters), and a primary keyword that a real person might search, such as "freelance UX designer [CITY]". Then write alt text (max 110 characters) for 6 images I describe: [DESCRIBE IMAGES]. Alt text must describe what is visible and why it matters, not stuff keywords. Do not promise rankings.

Why it works: Limits keep snippets from being truncated, and the alt text rule favours accessibility. What to expect / check: Specific, natural titles. Avoid duplicates across pages. Iterate: "Rewrite the home page title to include my city without sounding stuffed."

Accessibility and performance review

Act as a front-end reviewer. I will paste the text of my portfolio page and describe its layout. Create a checklist covering: heading order, link text that makes sense out of context, colour contrast (teal #0E6B6B on white), alt text, keyboard focus, form labels, image sizes and formats, and mobile tap target sizes. For each item, tell me how to check it in a browser, and which items require a real test with a screen reader or on a phone. Do not claim anything is compliant; give me ways to verify. Page content: [PASTE].

Why it works: It asks for ways to test, not for blanket assurance. What to expect / check: Run the checks yourself; a chat model cannot measure your live page. Iterate: "Give me the three highest-impact fixes if I only have 30 minutes."

Launch day checklist

Create a launch checklist for a new portfolio site on a hosted platform. Include: domain and HTTPS check, contact form test, favicon and social sharing image, 404 page, analytics with a cookie notice if required in my region, privacy page, broken link check, permissions for every case study (client approval for confidential work), backup and renewal dates, and a post-launch plan to update one case study per quarter. Format as a table: task | how to check | done (yes/no). Keep it under 25 items.

Why it works: Launch tasks are numerous and easy to forget. What to expect / check: Adapt to your platform's real settings. Iterate: "Add a one-week post-launch review with five questions to ask a friend who has never seen the site."

Worked example: from generic to specific

Prompt 1: "Make me a portfolio website."

Typical result: A generic template with filler text, invented projects and testimonials, lorem ipsum, and no idea who the visitor is.

Prompt 2:

Create a portfolio site for a freelance UX designer. Visitors: hiring managers skimming for 90 seconds. Pages: Home, 3 case studies, About, Contact. Teal accent, serif headings, generous whitespace, mobile-first. Use bracketed placeholders for any content I have not supplied; do not invent projects, clients, testimonials or numbers.

Why it is better: It names the audience, structure and style and forbids invented proof.

End-to-end workflow

1. Run the site brief prompt and gather the content list.
2. Write one case study from notes; get one strong example live first.
3. Feed the builder prompt with real headings and placeholders.
4. Paste in the About, microcopy and metadata.
5. Run the accessibility and performance review, then fix and retest.
6. Launch with the checklist and ask two people to try the site on their phones.

For more on hosting-based sites, see Hostinger AI prompts for local service business websites. To prepare for conversations the site will start, see 13 best AI prompts for job interview preparation.

Troubleshooting

| Problem | Likely cause | Fix | |—|—|—| | Site looks like every template | Generic brief | Add audience, point of view and distinct typography | | AI invented testimonials | No prohibition | Add "do not invent testimonials, clients or numbers" | | Case studies feel thin | Notes too short | Supply decisions, constraints and what you rejected | | Page loads slowly | Large images | Resize and compress images before upload | | Few enquiries | Unclear call to action | One primary action per page |

Review checklist before launch

• Every project, claim and number is true and approved by the client where needed.
• Placeholders in brackets are gone.
• Contact form works and has spam protection.
• Privacy information and cookie notice meet the rules where you work.
• Contrast and alt text have been checked.
• The site loads acceptably on a mobile connection.

FAQ

Do I need Hostinger's AI builder for these prompts?

No. The prompts work with any AI writing assistant; use the builder's current features for layout.

Can I show confidential client work?

Only with written permission, and consider anonymising details.

How many case studies should I include?

Two to four strong ones usually beat ten thin ones.

Should I write the copy myself?

Draft with AI if it helps, but rewrite in your own voice and verify every fact.

Can AI generate my project images?

Avoid presenting generated images as real project work; use real screenshots with permission.

Conclusion

A portfolio is evidence. Use AI for structure, drafts and checks, but fill it with your real projects, decisions and voice. With the prompts above, Jonas can move from PDF to a considered, honest site in one weekend.