8
23 Comments

I spent a month optimizing two sites for AI citations (GEO) and got zero results — here's the actual diagnosis

I've been running GEO (Generative Engine Optimization) experiments on two sites for about a month. Neither site got cited by ChatGPT or Perplexity once.

Today I finally sat down and diagnosed why.

The answer was embarrassing: Google hadn't indexed a single blog post on either site. 20+ articles each, zero indexed. The GEO chain is: Google indexes → AI crawlers discover → AI cites. I hadn't even cleared the first step.

Root causes:

  • No external backlinks at all, so Googlebot had no reason to prioritize crawling
  • No IndexNow setup, so Bing (which powers ChatGPT search) was never notified of new posts
  • Both sites had FAQPage sections in HTML but no JSON-LD schema markup
  • No llms.txt on one of the sites

Fixed today:

  • Manually requested indexing via GSC for the 10 best posts across both sites
  • Set up Bing Webmaster Tools and verified both domains
  • Bing meta tag deployed to both sites
  • Confirmed FAQPage JSON-LD was already in the template (missed this one — it was already there)

The GEO playbook I wrote says "expect 4-8 weeks after indexing." The clock hadn't even started.

I wrote up the full methodology at alexsignal.com/blog/how-long-does-it-take-to-get-cited-by-ai-search-engines-after-publishing-2026 — the irony of the domain not being indexed is not lost on me.

Sharing this because I suspect a lot of people doing "GEO" are in the same boat without realizing it.

on August 12, 2026
  1. 1

    Since you now have two sites and a real before and after, log the answers not just the index state: date, question, engine, and whether the answer named you or a competitor or nobody. Ten fixed buyer questions run weekly is enough, and after 30 days the pattern per site is readable even with zero citations, because "nobody gets named" is itself a finding. If you want that as a ready made 30 day setup with the prompts and a tracker sheet, I sell it as a $29 one time lab, no subscription.

  2. 1

    The useful diagnosis is that you were optimizing the top of a chain whose first dependency had failed. I would turn the recovery into a measured cohort: submission date, Google and Bing index date, crawler visits, first AI appearance, citation frequency, and referral traffic. That separates discovery from citation and shows whether the 4–8 week expectation is real for each engine.

  3. 1

    this is a genuinely useful post because the embarrassing answer is the common one: GEO isnt a separate magic layer, its classic SEO fundamentals wearing a new acronym. if google cant index you, theres no upstream for any AI to cite, full stop. a few things that unblock that first step fastest on a new site. 1) you nailed it on backlinks, a brand new domain with zero inbound links gives googlebot almost no reason to crawl deep, even a handful of real links from already-indexed sites shifts crawl priority fast. 2) internal linking, orphan posts with nothing pointing at them often just never get discovered, make sure every article is linked from something thats already indexed. 3) IndexNow plus Bing webmaster tools specifically, since Bings index is what ChatGPT search leans on, thats a direct pipe most people skip entirely. 4) once youre actually indexed, the thing that gets you CITED rather than just ranked is content that answers one specific question completely, with concrete numbers and named steps, because thats what a model can lift as a clean citation. vague listicles almost never get quoted. how many of the 20 posts are indexed now that you found the real problem?

    1. 1

      The IndexNow + Bing Webmaster Tools point is the one I’d missed most — I’d been treating Bing as a footnote to Google, but you’re right that it’s a direct pipe to ChatGPT Search. Adding that to the deployment SOP alongside the Google submission step.

      On your question: I ran the GSC coverage check after diagnosing the problem. 3 of roughly 20 articles are now confirmed indexed — the ones I manually submitted to Search Console on the day the post went up. The other 17 are either not indexed or not confirmed yet. The internal linking gap you described is almost certainly part of it — most of those articles have nothing pointing at them from already-indexed pages. That’s the next thing to fix before I do anything else with the content itself.

  4. 1

    The indexing step being the blocker is the part most GEO content completely skips. Every playbook I've seen starts at "write authoritative content" and assumes the crawl infrastructure is already solid. It rarely is, especially on newer domains or sites that launched quickly without a systematic submission process.

    The IndexNow/Bing Webmaster setup is probably doing more work than the GSC request here. ChatGPT's search layer pulls from Bing's index, so if Bing doesn't know your pages exist, you're invisible to ChatGPT regardless of how well-optimised the content is.

    Curious whether you're tracking time-to-first-citation separately for each site once indexing is confirmed, or treating them as one dataset. The domain authority difference between the two might show up in citation lag.

    1. 1

      Tracking per-site separately — the domain authority gap between them is significant enough that one dataset would mask which variable matters. One site has some external links from a product launch; the other has none. If citations do start appearing, that comparison will tell me more than absolute numbers.

      The Bing/ChatGPT chain was something I hadn’t fully internalized until setting up Webmaster Tools. Google indexed and Bing indexed turn out to be independent states. IndexNow was supposed to handle both, but I’d never verified the Bing side was actually receiving the pings — turns out it wasn’t, because the domain wasn’t verified in Webmaster Tools first.

  5. 1

    One more gate after indexing that nobody's named yet: most of the traffic citations eventually win you will be invisible. Assistants answer in place, so the reader who saw your brand in a ChatGPT answer either never visits, or shows up weeks later as direct traffic or branded search. Citation counts and your analytics will both undercount what GEO actually earned.

    Worth wiring the measurement side before the 4-8 week clock starts: a fixed basket of queries you re-run weekly to track share-of-answer (your leading metric while clicks stay invisible), plus an "asked an AI assistant" option in the signup "where did you find us?" question as the lagging one. Otherwise in two months you'll be diagnosing "GEO doesn't convert" with the same missing-plumbing problem, one layer up.

    1. 1

      The memory-off point is the one I would have missed. I’ve been running spot checks logged into ChatGPT — which means I’ve been quietly teaching it to recommend me, and the numbers look better than they are. Starting fresh sessions from here, cleared history.

      The versioned basket structure solves the drift problem I was already worried about — I’d been thinking about editing the query set as I learn more, which kills the trend line. Treating the initial set as a frozen cohort and adding new intent as a separate basket keeps the comparison valid.

      Adding two competitor-adjacent queries as a control group changes the whole framing from “things I want to win” to “baseline I can actually measure against.”

      Recommended vs listed instead of cited/not-cited is going into the tracking sheet now. The binary was already losing positional information I’ll want later.

    2. 1

      The measurement warning is the most useful thing in this thread. I’ve been proxying GEO performance by revenue — which is currently zero — without closing the loop between “cited” and “converted”. You’re right that those are two invisible-to-analytics steps.

      The “asked an AI” signup source question is going on both sites today; that one’s trivial to add and I have no good excuse for not having it.

      On the share-of-answer basket — what’s your approach to the query set? My instinct is 5-10 queries representing the exact intent I’m targeting, run weekly in ChatGPT and Perplexity, recorded manually. Crude but it closes the measurement loop that currently doesn’t exist. I haven’t found a clean automated way to do this without a dedicated tool.

      1. 1

        5-10 run weekly is the right size; three tweaks make the numbers trustable. Freeze the basket: the moment you edit queries week to week, the trend is gone, so version it and add new intents as a second basket instead of touching the first. Include two or three queries you don't expect to win (competitor-flavoured, adjacent) as a control group; if you suddenly show up everywhere at once, that's the model shifting under you, not your GEO working. And run the panel logged out with memory off, because your own usage teaches the assistant to recommend you and the numbers quietly inflate.

        Record position and framing, recommended versus merely listed, rather than a cited/not-cited binary. Manual is fine; the only real failure mode is skipping weeks.

  6. 1

    It reminds us that optimization will only help once we have the plumbing in place. ~

    It’s easy to jump straight into various techniques like schema, content structure and GEO tactics because they feel like the “interesting” stuff. If the content is not indexed by the search engines, then redirecting does not hold any significance.

    I always find it useful to check things in order: can the page be crawled, is it indexed, is it discoverable, and only then worry about performance.

    A key takeaway from the clock not even beginning. Occasionally, the optimal path is understanding which step you have yet to take.

    1. 1

      That ordering — crawlable, indexed, discoverable, then performance — is exactly the checklist I was missing. I had it backwards.

  7. 1

    Solid diagnosis — indexing is the first gate, and most GEO playbooks skip it. One thing I'd add: don't measure GEO by citation counts. A citation is a lead, not a conversion. The signal that matters is the conversation behind it — which assistant surfaced you, what the user asked, whether they clicked and acted. We built amami.dev to track exactly that, and it changed how we judge AI traffic.

    1. 1

      The “citation is a lead, not a conversion” framing is right — and it’s largely missing from how GEO is discussed. Where I am right now: I don’t yet have evidence that AI citations drive conversions on a cold site, because I haven’t generated a single citation to test it against. Will check out amami.dev once the indexing gate is cleared and I have something to measure.

  8. 1

    Zero indexed across 20+ articles explains the silence, but I'd expect the next month to stay quiet too, since models tend to cite the page that already has links pointing at it, not the newest one you pinged. Viewfy's citation checks keep surfacing answers assembled from Reddit threads and roundups rather than the vendor's own blog. The backlink gap is doing more damage here than the schema.

    1. 1

      The backlink gap is what I haven’t tested yet. My working hypothesis was that specificity beats authority for niche queries — ChatGPT doesn’t rank by PageRank the way Google does, so a direct, well-structured answer to a zero-competition query might not need links. But that’s still a hypothesis; I haven’t cleared the indexing gate long enough to generate evidence either way.

      Your Viewfy data point is the one I’d want to know more about: are the Reddit/roundup citations for queries where a direct vendor page existed but just had fewer links? Or is there genuinely no vendor page that answers the question directly? That distinction matters — it tells me whether backlinks are the deciding factor, or whether the question targeting is still wrong.

  9. 1

    The useful diagnosis is that GEO work has a dependency chain, and indexing is the first gate. I’d add a small preflight before every content batch: confirm pages are indexed, inspect crawl discovery, and test one query in both Google and Bing before interpreting citation results. Otherwise structured data and llms.txt can become activity without evidence. The 4–8 week clock also makes cohort tracking important: record publish date, index date, first citation date, and query type per page. That separates technical delay from a content or intent problem. Once the pages are indexed, will you compare the ten manually submitted URLs against untouched pages as a control? That would make the diagnosis much stronger.

    1. 1

      Cohort tracking is the right frame — I wasn’t recording index dates at all, just publish dates. Adding that column to the template now: publish → index → first impression → first citation.

      On the control comparison: yes, that’s the plan. I submitted 10 URLs that had the clearest topic focus and existing FAQ schema. The remaining ~30+ articles across the two sites stay untouched, which gives a natural comparison set. I’ll run a 4-week check on index status, GSC impressions, and citation queries in ChatGPT/Perplexity.

      One confound I’m already worried about: the submitted pages may also happen to be the better-written ones, so “indexed faster” and “higher quality” will be hard to separate. Will try to pick control pages of roughly similar depth.

      The pre-flight checklist is going into the deployment SOP either way. “Is this indexed?” before “why no citations?” is a two-second check I somehow never ran.

  10. 1

    This hits close to home. I just launched two apps — ***** and ***** realized I'd been so focused on the App Store that I never checked if Google had even indexed my landing pages.

    The IndexNow tip is gold. Setting that up today.

    One thing I'd add: for app landing pages specifically, I found that having a proper privacy policy and terms page (real URLs, not just in-app) helped with indexing speed — Google seems to treat those as trust signals.

    1. 1

      The privacy + terms URL trust signal is one I hadn’t specifically tracked — both sites have them but they’re auto-generated pages. Going to pull the GSC coverage report and see whether Googlebot has actually crawled those or skipped them along with everything else.

      Makes sense on the app landing page front. Google probably wants to confirm the site is legitimate before investing crawl budget on content pages.

  11. 1

    The “the clock hadn’t even started” realization is probably the most useful part here. Easy to spend weeks optimizing the final step of a funnel without checking whether the prerequisite step is actually working.

    1. 1

      Exactly — and what makes it worse: step 1 of my own GEO guide says “prerequisite: indexing.” I just never ran the check on my own sites. The irony of diagnosing other people’s setup while skipping the preflight on mine.

      1. 1

        That irony makes the lesson even better — knowing the prerequisite isn’t the same as actually checking it. Sounds like the kind of mistake you only make once.

    2. 1

      This comment was deleted 19 days ago