Make the rules part of the repository
A project instructions file is the most reliable place for search requirements. Keep it specific: which file holds metadata, which structured data types the site uses, and what must be true before a page is considered done.
- Define the done condition for a page: unique metadata, canonical, structured data, alt text, sitemap entry.
- Point at the existing pattern in the codebase so the agent extends it instead of adding a parallel one.
- Add a check to the test or lint step where possible, so a missing title fails before review.
The foundations AI builders skip most often
An AI builder optimises for what you can see. Search engines read what you cannot. These are the items missing from almost every site we audit, regardless of which builder produced it.
- A unique title and description per page — not the same pair repeated across the whole site.
- A self-referencing canonical link on every page.
- A social share image at 1200×630, referenced with an absolute URL.
- Descriptive alt text on every meaningful image.
- A sitemap that lists every public page, plus a robots.txt that does not block the site.
- One canonical host: https, and either www or non-www, with the other redirecting.
What AI search engines actually need (GEO)
Google's AI answers, ChatGPT, Perplexity and Copilot do not rank pages the way a classic results list does — they quote them. To be quoted, a page has to state the answer in plain sentences near the top, carry machine-readable structure around that answer, and be reachable without JavaScript. Most AI-built sites fail on the last two: beautiful layout, no structured data, and content that only appears after the page hydrates.
- Answer the question in the first paragraph, in one or two complete sentences — no build-up.
- Add JSON-LD for what the page actually is: Organization, LocalBusiness, Product, Article, Service.
- Keep headings honest: one H1 per page, H2s phrased the way people ask the question.
- Serve real HTML on first request, so a crawler that runs no JavaScript still sees the text.
- Publish an llms.txt and keep the sitemap accurate, so assistants can find the pages worth quoting.
Verify before release
Agents are good at breadth and occasionally careless about repetition. Before shipping, list every page with its title and description side by side — duplicates and placeholders stand out immediately.
- Confirm the sitemap matches the routes that actually exist.
- Confirm the canonical on each page points at itself on the production domain.
- Confirm structured data parses and describes the right entity.
Add this to your project instructions
Search and AI-search requirements for this repository: 1. A page is not done until it has a unique title, a unique meta description, a self-referencing canonical, structured data for its type, and alt text on every meaningful image. 2. Adding a public route also means adding it to the sitemap in the same change. 3. Content pages must render their main text server-side. 4. Each page opens with one or two sentences answering what it is about, so AI assistants can quote it. 5. Before release, list every route with its title and description and fix duplicates or placeholders.
A free Sitejump audit turns this generic checklist into a list of the exact gaps on your own site, with a prompt written for each one.
Claude Code SEO questions
Why is my Claude Code site not showing up in Google?
Usually one of three reasons: the pages have no unique titles and descriptions, the site was never submitted to Google Search Console, or the content only renders after JavaScript runs. Fix the metadata, verify the domain in Search Console, submit the sitemap, and request indexing for the main pages.
Does a Claude Code site need structured data?
Yes, if you want to be cited in AI answers. Structured data (JSON-LD) is how an assistant knows the page describes a business, a product or an article rather than just text. Without it, the page can still rank but is far less likely to be quoted.
Can Sitejump check my Claude Code site?
Yes. The free audit reads your live site, scores search and AI-search readiness, and lists what is missing. The improvement package then hands your builder the exact prompts to fix each item — no migration required, because the site already lives where you want it.
Building somewhere else?
Ask the AI assistant
More on getting cited by AI search engines
Sitejump is developed and operated by miPlug.