Tools

Website Prompt Generator

Pick where you work with AI and what you want to fix on your website. Get a ready-made prompt with guardrails that keep your AI on the job, and a list of what to check in its answer. Free, no sign-up.

Quick answer

This is a free AI prompt generator for fixing website SEO issues and the page basics non-coders often miss. Pick where you work with AI and one of 10 fixes, from page titles, meta descriptions and alt text to exposed secret keys and cookie consent. You get a written prompt with fixed guardrails: look first and report, stay inside one job, change one thing at a time, and stop and ask instead of looping. The prompt works in ChatGPT, Claude, Gemini, Claude Code, Lovable and other AI tools, and the generator calls no AI and needs no account.

Generate your prompt

How to use this

Start with where you work with AI: a chat assistant, an AI website builder or an AI coding agent. Then pick what you want to fix and press "Generate prompt". The note above the prompt tells you the one thing to add. For a builder or an agent, replace the part in square brackets with the page's name or address. For a chat assistant, paste the page's code at the end.

Copy the prompt and paste it into your AI. It reports what it finds and waits for you. Reply when the report makes sense, and let it make one change at a time. When it's done, go through the list of what to check in your AI's answer before you keep the change.

The 10 fixes, and what each one checks

Most of these live in parts of the page a visitor never sees: the head of the page's code, or scripts that load in the browser. That's why they get missed. Here is what each fix covers, where it sits on a page and what the prompt makes your AI check.

Structured data (schema / JSON-LD)

Structured data is a block of code, usually JSON-LD, that tells Google in a fixed format what a page is: an organisation, a product, an article. Visitors never see it. Google uses it to decide whether a page can show a rich result, such as a breadcrumb trail on desktop. The prompt makes your AI list every block first and check each value against what a visitor can actually see, because markup describing content that isn't on the page can cost the page its rich results. Adding markup from scratch? Our AI prompt for schema markup goes further.

Page title

The title sits in the page's head, inside the title tag. You see it in the browser tab, and it's one of the main things Google uses to write the clickable headline in its results. Google sets no fixed length, but it cuts long titles to fit the screen, so a good title says what the page is about early. A common problem on AI-built sites is one title set once for the whole site, so every page shows the same text. The prompt checks for exactly that, shows you the current title and asks for two or three options for you to choose from. It never hands you a character count as if it were Google's rule.

Meta description

The meta description is a short summary in the page's head. It doesn't show on the page itself; it's what can appear under your title in Google's results. Google mostly writes that snippet from the page's own content and uses your description when it describes the page better. So nothing guarantees it shows, but a clear, accurate description for each page gives Google its best option. AI-built sites often share one description across every page, and the prompt checks for that first.

Headings

Headings are the page's outline. The H1 is the main heading, H2s start sections and H3s start sub-sections. Screen readers and other assistive technologies use them to move around a page, and HTML guidance says a page should generally have a single H1. Problems usually come from text styled to look like a heading without being one, or a heading level picked for its size. The prompt maps every heading first and keeps the wording and the look exactly as they are.

Image alt text

Alt text is a short description attached to each image in the code. Screen readers read it aloud, and Google uses it to understand what the image shows. Good alt text describes the image in the context of the page, with no keyword lists. A decorative image gets empty alt text so screen readers skip it, and an image that's a link says where it goes. The prompt adds one rule that matters with AI: if your AI can't see an image, it asks you what the image shows instead of guessing from the file name.

Social share preview (Open Graph)

Open Graph tags sit in the page's head and decide what a shared link looks like: the title, description and image on the preview card in a chat app or a social feed. The Open Graph protocol asks for four tags on every page: og:title, og:type, og:image and og:url. When they're missing, or copied from the homepage onto every page, every shared link shows the same card. The prompt checks all four. To see the result, send yourself the live link in a message.

Whether Google can find the page

Five things on your own site affect whether Google can find and list a page. A noindex rule tells Google to drop it. The robots.txt file controls crawling. The canonical tag names the page's preferred address. The sitemap lists the addresses you want in search. And normal links from your other pages lead Google to it. This prompt only reports at first, because each of these can be set on purpose: a thank-you page may be hidden for a reason. Even with everything right, crawling can take days to weeks. Our guide to why an AI-built site isn't showing on Google explains each one.

Broken links

A broken link sends a visitor to a page that doesn't exist, the wrong section or nowhere at all. Watch for placeholder addresses left over from a first draft, links to pages that were renamed, and "links" that are really buttons run by scripts, which Google may not follow. The prompt lists every link first. It never lets the AI guess where a link should go or delete one: you decide, then click each changed link yourself.

Secret keys in the page's code

A secret key, such as the private key for a payment or email service, must never be in the code a visitor's browser downloads, because anyone can read that code. Some keys are made to be used in the page, and the provider's own documentation says which. The prompt makes your AI list anything that looks like a key without repeating its full value, and change nothing yet. A secret that was ever in public code needs replacing with a new one, not just moving. Our guide explains why an API key can't go in the frontend.

Analytics and cookie consent

Analytics and advertising scripts usually set a cookie in the visitor's browser, and a cookie ID can count as an online identifier, which POPIA lists as personal information. Asking first is the safest way to handle it, which means analytics loads only after a visitor accepts. This prompt covers the whole site's set-up, because the cookie banner and the analytics are usually shared by every page. It reports what loads and when before anything changes. Our guide to POPIA and Google Analytics explains the law and Google's Consent Mode.

Why the prompt changes with where you work with AI

Which AI you use matters less than what it can see. A chat assistant that isn't connected to your project knows only what you paste, so its prompt ends with a space for the page's code and tells it to ask for anything else instead of guessing. An AI website builder and an AI coding agent both work inside your project, so their prompts name the page, ask for every changed file to be listed and say not to publish until you've checked. The agent's prompt also rules out installing or committing anything.

Why every prompt reports first and stops on a failure

The two most expensive mistakes with AI are a change made before anyone checked what was there, and a loop of fix after fix that drifts further from the problem. So every prompt has the same frame. Step 1 asks the AI what the site is built with and what it finds, then makes it wait. It changes one thing at a time. If a change doesn't work the first time, it stops and tells you instead of trying something new. Our guide to breaking vibe-code loops explains why that stop matters.

A worked example

Here is the prompt for "Write or fix my page title", in the AI website builder version:

I need help with one job on my website: write or improve the title of one page (the text in the browser tab, and one of the main things Google uses for the clickable headline in its results).

HOW YOU'LL WORK ON IT
You can see and edit this project's files, and I can't. So explain what you find and what you change in plain words, as if I've never read code.

SCOPE
Work only on [the page, e.g. the homepage or /contact]. Only the title changes. Nothing else.

STEP 1: LOOK FIRST AND REPORT
Before changing anything, tell me in one line what the site is built with (for example plain HTML, React, or a website builder's own system) and where this page's title is set. Tell me if one title is set for the whole site, so every page shows the same one. Then report:
- The page's current title, exactly as it is
- The page's main heading, and what the page is about in one sentence
- Whether any other page uses the same or nearly the same title
- Two or three options for a new title that meet the standard below, for me to choose from
Don't change anything yet. Wait for my reply.

THE STANDARD TO CHECK AGAINST
- Every page needs its own title that says what that page is about. Avoid vague titles like "Home" and the same title on many pages.
- Keep it descriptive and concise. Google sets no fixed length, but it cuts long titles to fit the screen, so say what the page is about early.
- No keyword stuffing: use a word once, not a list of variations.
- Add the site's name briefly if it helps, separated by a hyphen, colon or pipe.
- The title should match what the page's main heading promises.

DON'T TOUCH
- Don't change the page's layout, design or wording, any other page, or any file name or location.
- Don't change the page's headings, its web address or its description.

MAKING THE CHANGE
When I say go, make one change at a time. After each one, tell me what you changed, list every file you changed and wait for me to check it before the next. Don't publish the site; I'll do that once I've checked.

HOW TO CHECK IT WORKED
Tell me what I should see in the browser tab once the change is live, and check that other pages still show their own titles.

WHEN TO STOP AND ASK ME
Stop and ask me before going further if anything is unclear, if a fix would affect another page or a part other pages share (the header, the footer, a template), if you'd need to add a package, plugin or outside service, or if a change doesn't work the first time. Don't try a different approach on your own. Tell me what happened and what you'd suggest.

The builder's AI should come back with the page's current title, its main heading, whether other pages share the title and two or three options, then wait. A good follow-up from you picks one of its suggested titles and says go.

This tool or the Custom Prompt Builder?

Use this generator when your problem is one of the 10 fixes above: the prompt is already written and checked. Use the Custom Prompt Builder when the job is your own, in your own words, such as a new feature or a bug only you can describe.

What these prompts can't do for you

They give your AI a clear job and firm limits. They can't see your site, so they can't tell whether you named the right page, and they can't promise what any AI does with them. Read the AI's report before you say go, and check the answer before you keep a change.

Independent, and no guarantee of what your AI does

AI Build South Africa is an independent resource. We're not endorsed by, or an official partner of, any AI tool or platform named on this page, and we do participate in affiliate and referral programmes with some platforms. These prompts explain web standards and search guidance in plain words; they aren't legal advice, and they can't guarantee what any AI does with them, so check the answer before you keep a change. See our Disclaimer for the full disclosure and our Terms of Service for the wider terms.

Frequently asked questions

Is the Website Prompt Generator free, and do I need to sign up?

It's free, with no account, no sign-up and no usage limit. It runs in your browser and calls no AI: the prompts are already written, and your two choices only decide which one you see. Nothing you pick is sent to us or stored.

Does it work with ChatGPT, Claude or Gemini?

Yes. Pick "Chat assistant". A chat assistant that isn't connected to your project can't see your website, so that version ends with a space for the page's code, and the note above the prompt shows you how to copy the page's code.

Can I use it in Lovable or another AI website builder?

Yes. Pick "AI website builder". That version tells the builder's AI which page to work on, asks it to explain what it finds in plain words and to list every file it changes, and tells it not to publish the site until you've checked.

Can I use it with Claude Code or another AI coding agent?

Yes. Pick "AI coding agent". The agent reads your project's files itself, so the prompt asks it to report before changing anything, to list every file it changes and not to install, commit or publish anything.

What makes a good meta description?

One that sums up that specific page accurately in a sentence or two, written for a person choosing between results. Each page needs its own. Google sets no length limit but cuts long ones to fit the screen, and it mostly writes the snippet from the page itself, so a good description is a strong option, not a guarantee.

How do I fix duplicate meta descriptions?

Duplicates usually mean the site sets one description in a template every page shares. Pick "Write or fix my meta description": the prompt asks your AI where the description is set and whether other pages share it, then helps you write one page's description at a time.

What should alt text include?

What the image shows, in the context of the page, in plain words, with no keyword lists. A decorative image gets empty alt text (alt="") so screen readers skip it, and an image that works as a link or a button says what it does or where it goes.

Why use these prompts instead of asking my AI in my own words?

Asking in your own words gets you only the limits your AI thinks to add. Every prompt here tells it to report before changing anything, stay inside one job, make one change at a time and stop after a failed attempt instead of looping. It also spells out the standard to check against, taken from Google's documentation and web standards.

Related reading