C. Website Launch Readiness · Prompt 25

SEO & Shareability Foundations

Get the free PDF

Why it matters

If a crawler or a chat app cannot read a page, the site is hard to find and shared links look empty.

Modeled on

Google Search Central guidance, Lighthouse SEO checks, and the Open Graph protocol.

How to run this prompt

Switch to a mode that does not edit files. In Cursor that is Ask or Plan. In Claude Code that is Plan mode.
Paste the audit prompt. Wait for the report. It must stop and ask which IDs to fix.
Read the report. Keep the IDs you agree with.
Switch to a mode that can edit. Paste the fix prompt and the IDs you chose.
Switch back to the read-only mode and paste the same audit prompt again. Confirm those IDs are gone.

Cursor: audit in Ask mode or Plan mode. Fix in Agent mode.
Claude Code: audit in Plan mode (Shift+Tab cycles to it). Fix in Normal mode, which can edit.
Any other tool: audit in Chat, Discuss, or Plan mode, whichever answers without editing files. If the tool has no such mode, the prompt itself forbids edits. Fix in the mode that is allowed to edit files.

The audit prompt

MODE: AUDIT ONLY. Do not create, edit, or delete any file. Do not run commands
that change anything: no installs, migrations, git commits, deploys, or "--fix" flags.
If your tool has an Ask, Plan, Chat, or Discuss mode, use it for this prompt.

Before you start:
- Tell me the stack you detect (framework, language, database, auth, hosting,
  payment provider) and which folders you will review.
- If a check below does not apply to this stack, write "Not applicable" and why.
- If you can run read-only commands, run the ones listed. If you cannot, list them
  so I can run them and paste the output.

SEO & Shareability Foundations: what to check
Audit SEO and link previews from the code and the built HTML if a build exists. Do not submit the site to a search engine.
1. List pages and their title and meta description. Titles do not have a fixed length. They are often cut off in results around 50 to 60 characters. Meta descriptions do not change ranking. They can be cut off around 150 to 160 characters. Flag duplicates and framework default titles such as "Vite + React".
2. Check each page for one h1, a sensible heading order, and link text that says where it goes.
3. Check Open Graph and Twitter tags: title, description, image, and url. The image should be 1200 by 630. Say if any page is missing them.
4. Check the favicon, apple touch icon, and web manifest. Flag the framework default icon if it is still there.
5. Read robots.txt. It should allow public pages and must not disallow the whole site by accident. Note noindex on pages that should be public.
6. Check sitemap.xml includes the public pages and is linked from robots.txt. Thank-you or private URLs should be absent.
7. Check canonical URLs and whether www and non-www are consistent in config. A host-level redirect you cannot see is Needs manual check.
8. Confirm the main text is in the server HTML, not only inserted after JavaScript runs. View the built file or the response, not only the component.
9. Add structured data only where it matches the page (for example Article or Organization). Do not invent reviews or ratings.
10. Check the 404 page returns a real 404 status and links to useful pages.
11. Return a table: URL | title | description | OG image | issues. Do not edit files.

Evidence rules:
- Every finding cites a file path and line number, or the exact command output used.
- Mark each finding Confirmed (seen in the code) or Needs manual check (depends on
  something outside the repo, such as a dashboard setting or production data).
- Never print a full secret. Show the first 4 characters and the location only.
- If you are not sure, say so. Do not invent files, settings, or results.

Severity: Critical = exploitable now, or leaks real data or money. High = serious
with little effort. Medium = weakens defenses or needs a second bug. Low = hygiene.

Report:
- Summary: count of findings by severity.
- Table: ID | Severity | Confirmed? | Finding | Evidence | Why it matters | Suggested fix | Effort
  (IDs for this prompt use the prefix P25, for example P25-1, P25-2.)
- Checked and fine: what you verified is already OK.
- Could not check: what I need to look at myself, and where.

Then stop. Do not fix anything. Ask me which IDs I want fixed.

Get the free PDF

Related prompts

26. Conversion & CTA Audit

Share this prompt

WhatsApp LinkedIn X

How to run this prompt

Switch to a mode that does not edit files. In Cursor that is Ask or Plan. In Claude Code that is Plan mode.

Paste the audit prompt. Wait for the report. It must stop and ask which IDs to fix.

Read the report. Keep the IDs you agree with.

Switch to a mode that can edit. Paste the fix prompt and the IDs you chose.

Switch back to the read-only mode and paste the same audit prompt again. Confirm those IDs are gone.

Cursor: audit in Ask mode or Plan mode. Fix in Agent mode.

Claude Code: audit in Plan mode (Shift+Tab cycles to it). Fix in Normal mode, which can edit.

Any other tool: audit in Chat, Discuss, or Plan mode, whichever answers without editing files. If the tool has no such mode, the prompt itself forbids edits. Fix in the mode that is allowed to edit files.

The audit prompt

MODE: AUDIT ONLY. Do not create, edit, or delete any file. Do not run commands that change anything: no installs, migrations, git commits, deploys, or "--fix" flags. If your tool has an Ask, Plan, Chat, or Discuss mode, use it for this prompt. Before you start: - Tell me the stack you detect (framework, language, database, auth, hosting, payment provider) and which folders you will review. - If a check below does not apply to this stack, write "Not applicable" and why. - If you can run read-only commands, run the ones listed. If you cannot, list them so I can run them and paste the output. SEO & Shareability Foundations: what to check Audit SEO and link previews from the code and the built HTML if a build exists. Do not submit the site to a search engine. 1. List pages and their title and meta description. Titles do not have a fixed length. They are often cut off in results around 50 to 60 characters. Meta descriptions do not change ranking. They can be cut off around 150 to 160 characters. Flag duplicates and framework default titles such as "Vite + React". 2. Check each page for one h1, a sensible heading order, and link text that says where it goes. 3. Check Open Graph and Twitter tags: title, description, image, and url. The image should be 1200 by 630. Say if any page is missing them. 4. Check the favicon, apple touch icon, and web manifest. Flag the framework default icon if it is still there. 5. Read robots.txt. It should allow public pages and must not disallow the whole site by accident. Note noindex on pages that should be public. 6. Check sitemap.xml includes the public pages and is linked from robots.txt. Thank-you or private URLs should be absent. 7. Check canonical URLs and whether www and non-www are consistent in config. A host-level redirect you cannot see is Needs manual check. 8. Confirm the main text is in the server HTML, not only inserted after JavaScript runs. View the built file or the response, not only the component. 9. Add structured data only where it matches the page (for example Article or Organization). Do not invent reviews or ratings. 10. Check the 404 page returns a real 404 status and links to useful pages. 11. Return a table: URL | title | description | OG image | issues. Do not edit files. Evidence rules: - Every finding cites a file path and line number, or the exact command output used. - Mark each finding Confirmed (seen in the code) or Needs manual check (depends on something outside the repo, such as a dashboard setting or production data). - Never print a full secret. Show the first 4 characters and the location only. - If you are not sure, say so. Do not invent files, settings, or results. Severity: Critical = exploitable now, or leaks real data or money. High = serious with little effort. Medium = weakens defenses or needs a second bug. Low = hygiene. Report: - Summary: count of findings by severity. - Table: ID | Severity | Confirmed? | Finding | Evidence | Why it matters | Suggested fix | Effort (IDs for this prompt use the prefix P25, for example P25-1, P25-2.) - Checked and fine: what you verified is already OK. - Could not check: what I need to look at myself, and where. Then stop. Do not fix anything. Ask me which IDs I want fixed.