What to Do After You Find Out AI Isn't Citing Your Website: A 30-Day Fix Plan (2026)

Key takeaways

• Start with diagnosis, not rewriting. Most uncited sites have one of four problems: AI crawlers can't reach them, the content is the wrong type, the facts are stale or inconsistent, or nobody else mentions the brand.
• Fix crawler access in week one. No content change matters if the bot gets a 403 or an empty JavaScript shell.
• Product pages and landing pages earn about 39% of ChatGPT citations, so thin commercial pages are often the quickest win.
• Refresh on a schedule. Product pages and how-tos lose half their cited pages in roughly 74 to 77 days.
• Re-test with the same setup each time (private window, signed out, same location). One missed citation is noise; a pattern across 20 prompts is a signal.

Start by deciding whether you have a problem at all

A thread on r/DigitalMarketing asked the question every AEO person eventually hits: how do you tell "the site is invisible to AI" from "the site is fine, the model just didn't pick it that day"? Good question, and it deserves a real answer before you spend a month fixing things.

AI answers are probabilistic. Ask the same prompt five times and you may get five slightly different source lists. So a single screenshot of ChatGPT not naming you proves very little.

Here is a quick test I'd use:

• Run 15 to 25 prompts that matter to your business, each at least three times.
• Include branded prompts ("is [brand] legit"), category prompts ("best [category] for small teams"), and comparison prompts.
• Log whether you were mentioned, cited with a link, or absent entirely.
• Use one consistent setup: private window, signed out, same location.

If you're missing from nearly everything, including branded prompts, you have a structural problem (access, indexing, thin content). If you appear on branded prompts but vanish on category ones, you have a prominence problem. If you show up sometimes, you have a coverage problem, which is the most fixable kind.

Doing this by hand gets old fast. Tools like Promptwatch track prompts across ChatGPT, AI Overviews, Perplexity and others repeatedly, so you see rates instead of anecdotes.

There are also free one-off checkers if you only want a baseline, such as [tool:answergist] and [tool:rightchoice-ai]. They give you a snapshot, not a trend, but a snapshot is enough to start.

The 30-day plan at a glance

Week 1: diagnose and unblock

Day 1 to 2: build your baseline

Build the prompt list described above and record the results in a spreadsheet. Add a column for which sources got cited instead of you. That column becomes your target list later.

If you'd rather not babysit this, a tracker does the same job. Options in the same category include [tool:otterly-ai], [tool:peec-ai] and [tool:profound], though many of them stop at monitoring. For the broader field, the GEO software directory at bestgeosoftware.com lists them side by side.

Day 3 to 4: check crawler access

This is the most boring step and the one with the highest payoff. Pepper's write-up on lost AI Overview visibility puts it bluntly: no amount of content improvement matters if the crawler can't reach the page. I agree completely.

Check these in order:

1. robots.txt. Are GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot and Google's agents allowed? Many sites inherited a blanket block from a 2023 panic about training data.
2. CDN and WAF rules. Cloudflare, Fastly and Akamai bot-fight modes quietly return 403s to AI user agents. Your robots.txt can say yes while your firewall says no.
3. Rendering. If your content only appears after client-side JavaScript runs, many AI fetchers see an empty page. Confirm server-side rendering, or use a prerendering service such as [tool:prerender-io].
4. Status codes and redirects. Chains, soft 404s and login walls all look like missing content.
5. Sitemap. Submit a clean XML sitemap with only live, canonical URLs.

Then separate training bots from answer-time fetchers. Blocking a training crawler is a legitimate business choice. Blocking the bots that fetch pages when a user asks a question means you've opted out of being cited.

The best evidence here is your own server logs. Promptwatch Data tracked three months of weekly IP-verified AI crawler requests (June 8 to September 6, 2026) and found OpenAI made up 79.8% of verified requests in the final week, down from 94.8% in early June. Compare your logs to that mix. If a provider is a big share in the benchmark but near zero in your logs, you're probably blocked or unreachable for it. Only requests from the operator's published IP ranges count in that data, so spoofed user agents don't inflate the numbers.

For log work, [tool:screaming-frog-seo-spider] can crawl as different user agents, [tool:fandangoseo] and [tool:oncrawl] analyze logs, and Promptwatch's crawler analytics reads logs from Cloudflare, Vercel, Fastly or raw server files.

It is worth checking indexing too. Google AI Overviews lean on Google's own index, so a page missing from [tool:google-search-console] won't be cited there. Bing matters as well, since several assistants draw on it.

Day 5 to 7: confirm it's not a ranking problem

If you used to be cited and stopped, find out whether it's an AI problem or a plain ranking loss. Check Search Console for the same queries. If rankings fell, you have an SEO issue, and fixing it is the cure. If rankings held but citations dropped, look for a model change, a retired schema type or a freshness gap, as the Pepper piece suggests. Each has a different fix, and rewriting the entire site fixes none of them.

Week 2: fix the pages AI actually cites

Match your content to what gets cited

Promptwatch Data's analysis of which content types ChatGPT cites (September 28 to October 4, 2026) is useful here, because it shows that a lot of the work is on pages many teams neglect.

Product and landing pages together are 39% of citations. If your product pages are thin, full of slogans, or hide pricing behind a form, that's likely where you're losing. For branded prompts the pattern is stronger: product pages hit 23.3%, landing pages 22.8%, and reviews 5.6%, more than three times their overall share.

In practice:

• Put specs, plan names, prices, integrations and who it's for in plain text on the page. Replace "plans from $29" with the actual plans and prices.
• Date the facts that change.
• One fact per sentence. Models quote sentences, not vibes.
• Keep documentation public and crawlable. Docs were 7.5% of citations overall and are the biggest source type for software prompts.

Lead with the answer

Put a direct, self-contained answer in the first 80 words or so of the page or section, then add the context. This is the single most repeatable structural fix I've seen recommended, and it costs nothing.

Rebuild your FAQ properly

FAQ pages are only 3.3% of citations, but branded prompts cite them at 4.8%, so a brand FAQ is worth having. Most FAQs fail because the questions are written like marketing ("Why choose us?") and the answers ramble. Frame each entry as a real question someone would type, give the answer in the first sentence, and keep headings hierarchical. Build the question list from real prompts rather than guessing; [tool:answerthepublic] and [tool:alsoasked] are decent sources, and Search Console queries are better.

A caution on schema: FAQ and HowTo markup was retired or heavily reduced by Google. If that markup was carrying weight for you, restructure the content into clean, extractable prose and use current types instead of leaving a gap. Organization schema with sameAs links to your official profiles is still worth adding, and a platform like [tool:schema-app] can manage it at scale.

Fix contradictions on your own site

Search your own domain for old facts: site:yourdomain.com pricing, site:yourdomain.com hours, and the outdated number in quotes. Old announcement posts and archived promo pages are the usual culprits. Keep core facts on one canonical page and make everything else agree with it. Update, redirect or delete the rest, then request a recrawl in Search Console.

Build the missing pages

Compare your prompt baseline with your site map. Where there is a prompt ("X vs Y", "best X for Z", "is X worth it") and no page that answers it, that's a gap. Content tools can help produce drafts, such as [tool:frase], [tool:clearscope] or [tool:surfer-seo], but the facts have to come from you. Generic AI filler won't get cited because it adds nothing the model doesn't already have.

Week 3: fix what other sites say about you

Own-site fixes only go so far. For commercial prompts, listicles (13.6%) and comparisons (5.9%) are heavily cited, and you don't control most of them.

Get into the roundups

For each category prompt where you're absent, open the sources that were cited. If it's a "best of" article, find the author and pitch with something concrete: a data point, a free trial, a specific differentiator. Vague outreach gets ignored. Publish your own comparison pages too, and be honest in them, because models tend to pass over pages that are obviously one-sided.

Outreach tools like [tool:crowdreply] and [tool:mentionagent] exist for this, and [tool:mentionbird] helps you see which sources AI cites in your category. Be careful with anything that automates the human part. Editors can tell.

Clean up listings and facts

Build a grid of every place your business facts live: Google Business Profile, directories, Wikipedia if you have a page, review sites, social bios. Fix mismatches. Don't edit Wikipedia yourself; post an edit request on the talk page, disclose your connection and cite a reliable source. For multi-location brands, [tool:yext], [tool:synup] or [tool:moz-local] can sync listings.

Reviews

Reviews are a small share of citations overall but a big one on branded prompts. Collect them on the sites that matter in your category, such as [tool:trustpilot] or G2 for software. Reply publicly and politely with correct facts when something is wrong.

A note on Reddit and social

Don't build the plan around Reddit. Promptwatch Data shows reddit.com's share of ChatGPT citations fell from about 4% to 0.5% on August 14, 2026, and in the week of September 28 to October 4 ChatGPT took only 0.46% of citations from social platforms, against 12.2% for Google AI Overviews. So social presence matters far more for AI Overviews than for ChatGPT. Know which engine you're optimizing for.

The LinkedIn post above makes a point that's easy to skip: test whether AI can actually reference your content, rather than assuming that publishing is enough.

Week 4: measure, then set up the loop

Re-test with the same setup

Run the baseline prompts again, same window, signed out, same location. Compare mention rate, citation rate and which competitors replaced you. If nothing moved after a month, go back to diagnosis. You may have fixed a page the AI wasn't reading while the real source is still out there.

Expect slow movement. Fixes can take two to four weeks to show up, and some engines refresh faster than others. A 30-day plan gives you a first read, not a verdict.

Measure the traffic, not just the mentions

Mentions are a vanity metric if nobody clicks. Tag AI referrals in your analytics and watch conversions from them. Promptwatch's visitor analytics ties AI traffic to the pages involved, and [tool:usermaven] or your regular analytics can handle simple referral segments.

Schedule refreshes

Promptwatch Data's content half-life study tracked every page ChatGPT cited on July 6, 2026 through early October. Results:

Product pages, reviews and how-tos reach their half-life after 74 to 77 days. News loses half its pages by day 36. The practical reading: refresh product pages and how-tos about every two months, treat news as a short burst, and expect landing pages and docs to last longest. One tracked refresh program across 200-plus pages reportedly lifted citation rates from 12% to 47% using a steady freshness cadence, which beats one-off rewrites. That's a single vendor's figure, so treat it as directional.

Put it on a calendar

• Weekly: check crawler logs and errors.
• Monthly: re-run the prompt set and update the scorecard.
• Every 60 days: refresh product pages and how-tos.
• Quarterly: audit third-party listings and roundup coverage.

If you want the checking and fixing to run as a loop rather than a spreadsheet, Promptwatch's Action Board and Content Agent are built for that, turning gaps into prioritized tasks and drafts, then tracking whether the published pages got crawled and cited. Other tools that lean toward execution include [tool:searchatlas-llm-visibility] and [tool:gradial-geo]. More options are listed at ai-rank-tools.com.

Common reasons the plan doesn't work

• You fixed content but never checked the firewall.
• You measured after four days.
• You changed ten things at once and can't tell what helped.
• Your product page is great but your pricing sits in a PDF or behind a form.
• You optimized for one engine, then judged results on another.
• Competitors are simply cited by more third-party sources, which no on-site edit fixes.

If you'd rather not run this alone

Some teams don't have the hours. An agency that does technical SEO, content and AI search work can run the plan for you; 1001 SEO Media is one that does this, with monthly reporting and no long-term contracts. If you stay in-house, the plan above works with a spreadsheet and some patience.

A final checklist

1. Baseline prompt log built, with repeats.
2. robots.txt, CDN and WAF allow answer-time AI fetchers.
3. Key pages render without JavaScript.
4. Product and landing pages state facts, prices and specs plainly.
5. Answer-first openings on priority pages.
6. Brand FAQ published.
7. Contradictory facts removed from your own site.
8. Listings and third-party profiles consistent.
9. Pitches sent to roundups you're missing from.
10. Re-test done with the same setup, refresh calendar set.

Day 31 is when the real work starts, because the sites that get cited steadily are the ones that keep checking.