A DLVX track · 10 guides · Updated 20 October 2026

Get Found.
Search and AI visibility.

How we get businesses found on Google, in maps and in AI answers. What actually works, what is hype, what you can skip, and the order to do it in. The same methods run in our own engine every night.

96 sources, each with its date

19 October 2026 newest source

10 guides, read in order

  1. 01 · Start here

    What works in search and AI visibility in 2026

    Every method we use to get businesses found on Google, in maps and in AI answers: what works, what is hype, and the order to do it in.

    25 min read
  2. 02 · Foundations

    Get indexed: Search Console, sitemaps and IndexNow

    How pages actually get found and indexed in 2026: sitemaps with honest dates, Search Console, IndexNow, robots rules and AI crawlers.

    14 min read
  3. 03 · Foundations

    Structured data and your entity, without the myths

    What schema markup still does in 2026, what it does not do for AI answers, and how to make engines sure who your business is.

    12 min read
  4. 04 · Local

    Local and map visibility that lasts

    How a local business gets found on Google Maps and named in AI answers: the profile, real reviews, honest local pages and how to track it.

    12 min read
  5. 05 · Write it

    Write pages that AI answers can cite

    How we write pages that AI answers cite: answer first, original evidence, honest dates, and AI as a helper rather than a page factory.

    12 min read
  6. 06 · Words

    Query fan-out: write for the searches AI runs

    AI answers search for short hidden queries, not the question typed. How we harvest them and put the words on one page per intent.

    14 min read
  7. 07 · Words

    Mine your long-tail searches

    Find the four-word-plus questions already in your Search Console, score them, and answer them on the page that ranks.

    12 min read
  8. 08 · Structure

    Internal linking that moves pages

    The cheapest search work you control: links from pages that already discuss a topic, with honest anchors, two to five at a time.

    11 min read
  9. 09 · Measure it

    Measure AI visibility without fooling yourself

    How we measure AI visibility honestly: first-party reports, a frozen prompt set, valid answers only and the maths that stops false wins.

    12 min read
  10. 10 · Judge it

    Triage any SEO tactic in ten minutes

    Our method for any SEO or AI search tip: grade the claim, check the rules and the law, decide, and measure before it changes anything.

    11 min read

Our own data behind these guides

Where a guide quotes a number of ours, it comes from one of these records. Each is a measurement from our own tools, not a study of the whole market.

dlvx.co Search Console performance, 19 July to 16 October 2026

DLVX (own Search Console, dlvx.co) · data to 16 October 2026

  • Web search, final data: 42 percent of clicks (22 of 52) came from queries Search Console does not list in its query report (anonymised queries)
  • Full question queries appear with real impressions, e.g. 'does claude work in thailand' (10 impressions, average position 11.3) and 'is claude available in thailand' (3 impressions, position 10)
  • Mobile CTR 2.2 percent at average position 8.7 vs desktop 1.2 percent at 12.6 in the same window

ChatGPT fan-out harvests, logged-out temporary chats

DLVX (Growth Engine harvest) · data to 11 October 2026

  • Hidden search queries captured over a set of unbranded buyer prompts: 1 to 4 per prompt, usually 2
  • A personalised (logged-in) chat put the brand name into the hidden query; logged-out temporary chats did not
  • Harvests repeat every 28 days on a stable prompt file; one harvest is a sample, not a verdict

Growth Engine scoring, indexing and probe rules

DLVX (Growth Engine operating notes) · data to 19 October 2026

  • Manual 'request indexing' in Search Console allowed about 10 to 12 URLs per property per day in our use; Google does not publish the number
  • An AI visibility figure is only reported as a pooled mention rate over 4 weekly runs with at least 60 valid answers; a change is a win only beyond 2 standard errors of the difference
  • Every probe answer is checked for validity (quota pages, sign-in walls, cut-off answers are excluded); no rate is quoted on fewer than 10 valid answers
  • A decision whose measurement window spans a Google core or spam update is marked inconclusive unless the effect clears twice the noise band
  • IndexNow pings go out only for new URLs or URLs whose sitemap lastmod changed; the key file must be live first