wowprompt

JavaScript rendering SEO check for React and single-page app sites

Compares what a page sends in its raw HTML with what appears after JavaScript runs, and finds the content, links, titles and structured data that search engines may miss on React, Vue, Angular or other client-rendered sites. Use it when a modern web app ranks poorly or Search Console shows pages crawled but not indexed.

A side-by-side check of raw HTML against rendered content for key page elements, with pass or fail marks and a fix list ordered by impact
The output this prompt produced, unedited.

The prompt

What to give

  • Site type and framework: [e.g. a React single-page app on a custom router, or Next.js with some client-only pages]
  • Pages to check: [paste URLs, one of each template: home, category, product or article]
  • Raw HTML of one page as served, from view-source: [paste the head and the first part of the body]
  • Rendered HTML of the same page, from the URL Inspection tool or browser DevTools: [paste the same parts]
  • Search Console indexing status for these pages: [e.g. crawled, currently not indexed]

Check every template

  1. Title, meta description and canonical tag: present in raw HTML, or only added by JavaScript.
  2. Main heading and body text: present before scripts run, or empty containers filled later.
  3. Internal links: real anchor tags with href values, or click handlers on div or button elements.
  4. Structured data: in the raw HTML, injected later, or missing.
  5. Status codes: a missing page returns 404, not a 200 with an error message drawn on screen.
  6. Lazy content: reviews, prices or descriptions that load only on scroll or click.
  7. Routes: each view has its own URL without a hash fragment.

Output format

  1. | Element | In raw HTML | In rendered HTML | Risk | Fix |
  2. A verdict for each template: fine, at risk, or broken for search.
  3. A fix list in priority order, naming whether the fix is server rendering, static generation, pre-rendering of key routes, or a smaller change.
  4. Three tests to repeat after the fix, with what a pass looks like.

Guardrails

  • Judge only from the HTML pasted; say "not checked" where a part was not provided.
  • Do not recommend dynamic rendering for bots only as the long-term answer; prefer the same HTML for users and crawlers.
javascript seoreact seosingle page app seoclient side renderingserver side rendering seorendering audit

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity