Prompt
Audit the attached code for issues that could affect visibility in Google and AI search.
Base your findings on the supplied code. Don’t assume that using React, Next.js or JavaScript automatically makes a page inaccessible.
Check:
- Content accessibility: Are the main headings, body copy and links present as HTML, stored only in JavaScript data, or inside hidden containers? Distinguish content that needs JavaScript to be fetched from content that needs JavaScript only to become visible.
- Indexability: Check robots directives, canonical tags and any apparent indexing conflicts.
- On-page SEO: Review the title, meta description, H1, heading structure and whether the copy clearly explains what the page offers.
- Internal links: Check whether navigation and relevant links use crawlable <a href> elements.
- Images: Review alt text and image markup.
- Structured data: Check its validity and consistency with the page content.
Return:
- A brief verdict.
- A table of issues with priority, evidence from the code, likely impact and recommended fix.
- The three most important actions.
- Any additional tests needed to confirm issues.
Separate confirmed findings from potential risks. Mark anything you cannot determine from this HTML as “Requires testing.” Don’t claim that Google or an AI crawler cannot access the page without evidence, and don’t invent missing information.
If no meaningful issue is found in a category, say so.
How to use it
- Tap Copy prompt.
- Paste it into your AI tool and attach or paste the page’s code.
- Run it, then use the “Requires testing” items as your follow-up checklist.