Field notes, with the instrument attached

What we have actually tested about crawler access, extractability, schema and citation behaviour, with the instrument and the date attached to every number.

Guide8 min read

How to Appear in AI Overviews

If you want to appear in AI Overviews, make your pages easy to fetch, parse, quote, and trust. The hard part is not tricks, it is removing extraction friction and publishing facts worth citing.

Read
Guide10 min read

Generative Engine Optimization Guide

A practical generative engine optimization guide starts with extractable facts, crawlable HTML, and pages built to be cited without losing caveats. It fails when teams chase folklore, hide answers in JavaScript, or expect weak sources to outrank better evidence.

Read
Comparison9 min read

AI Driven SEO Platforms Shortlist

If you want AI driven SEO platforms, shortlist tools by the job you actually need done: visibility tracking, prompt monitoring, or site fix prioritization. Most teams buy overlap, then discover the real constraint is weak source pages.

Read
Comparison9 min read

GEO Tools Working Shortlist

Most GEO tools are better at monitoring prompts than fixing the reasons you are not cited. Use them for tracking, then fix extractability, crawl access, and source clarity yourself.

Read
Guide8 min read

How to Rank in ChatGPT

How to rank in ChatGPT is mostly about being easy to retrieve, easy to quote, and hard to confuse. That means clean source pages, stable facts, and evidence outside your own site, not folklore tactics.

Read
Guide10 min read

How to Get Cited by ChatGPT

If you want ChatGPT to cite your site, make the page easy to fetch, easy to extract, and easy to trust. Then remove the structural mistakes that cause assistants to cite someone else.

Read
Guide9 min read

AI Overviews Optimization Guide

AI overviews optimization is mostly about making your pages easy to extract, qualify, and cite. That means cleaner facts, stronger page structure, and fewer rendering mistakes, not folklore tactics.

Read
Comparison9 min read

Generative Engine Optimization Tools shortlist

Most generative engine optimization tools are better for monitoring than fixing. Use them to find citation gaps, then repair extractability, rendering, and source clarity on site.

Read
Comparison10 min read

Best Answer Engine Optimization Tools

The best answer engine optimization tools help you measure citations, prompt visibility, and extractability gaps. None fixes weak source pages by itself, so the shortlist only matters if you pair tooling with site changes.

Read
Comparison10 min read

Profound Alternatives

If you are looking for profound alternatives, the right choice depends on whether you need measurement, workflow, or source-page fixes. Most teams should shortlist a tracker, Bing data, and a manual citation QA process before buying a broad platform.

Read
Comparison9 min read

Peec AI Alternatives: Realistic Options

Peec AI alternatives exist, but they solve different problems. The right choice depends on whether you need visibility tracking, technical extractability fixes, or a lighter manual workflow.

Read
Comparison9 min read

Answer Engine Optimization Tools

If you are evaluating answer engine optimization tools, start by separating prompt tracking, citation discovery, crawler debugging, and extractability checks. No single tool covers all four well, so the right shortlist depends on whether your problem is visibility measurement or source-page fixes.

Read
Guide8 min read

LLM SEO Tools, Working Shortlist

Most LLM SEO tools are really monitoring tools, not ranking levers. The useful shortlist depends on whether you need visibility tracking, extractability fixes, or workflow support.

Read
Comparison8 min read

ChatGPT SEO Tools Working Shortlist

Most ChatGPT SEO tools do not improve visibility by themselves. The useful ones help you find citation gaps, extraction failures, and pages AI systems can quote cleanly.

Read
Guide9 min read

Replace Text Screenshots With HTML?

If a sentence needs to be found, extracted, or cited by AI assistants, it should usually exist as HTML text on the page, not only inside an image. Keep screenshots for proof, not for carrying the primary claim.

Read
Guide9 min read

llms.txt on Subdomains or Main Domain?

Publish llms.txt on each subdomain only if that subdomain hosts public docs you want AI systems to discover. Do not expect ranking or citation gains from the file itself.

Read
Guide8 min read

Method caveats before or after answer?

Put the direct answer first, then place methodology caveats immediately after it or inside the same sentence. If caveats lead the page, extraction gets weaker. If caveats sit too far away, AI summaries often drop them.

Read
Guide8 min read

Pasted Spreadsheet Tables and AI Retrieval

Yes, sometimes. AI assistants can retrieve facts from pasted spreadsheet tables when the HTML is clean, headers are explicit, and caveats live inside the table context, not far away.

Read
Guide9 min read

Desktop vs print views for AI facts

Separate desktop and print views do not automatically hurt AI retrieval. Problems start when the print version carries the clean facts and the desktop page hides, rewrites, or fragments them.

Read
Guide8 min read

When Author Notes Break AI Extraction

Author notes help readers trust a page, but they often break the clean path an AI assistant needs to lift the main answer. The fix is placement and role clarity, not removing human voice.

Read
Guide9 min read

Move old claims to archive URLs?

Move old claims onto archive URLs when the historical version can still be useful, but should no longer compete with your current source of truth. If both versions stay on one URL, AI assistants often detach dates, caveats, and status labels from the claim itself.

Read
Guide9 min read

Verdict boxes vs canonical facts

Do not make the verdict box the only place a claim lives. Keep canonical facts in stable body sections, then let the verdict summarize them without changing scope or wording.

Read
Guide9 min read

Put Evidence Above Charts for AI Citation?

If the claim is buried inside an interactive chart, AI assistants may miss it or cite a weaker page instead. Put the key evidence in plain HTML above the chart, then let the chart add exploration, not exclusivity.

Read
Guide9 min read

Inline correction notices and AI fact retrieval

AI assistants can retrieve facts from pages with inline correction notices, but only when the current fact is easy to isolate and the retired fact is visibly demoted. If your correction note is vague, buried, or stylistic, you raise the odds of a bad citation.

Read
Guide9 min read

When abbreviations hurt AI citations

Abbreviations help human readers move faster, but they often weaken extraction when the model has to decide what a term means. The risk rises when the short form appears before the expanded term, changes by section, or sits far from the fact being cited.

Read
Guide9 min read

Mixed glossary and guide pages for AI

AI assistants can retrieve facts from pages that combine definitions and how to guidance, but only when the page makes the primary answer obvious. If definitions, examples, and instructions blur together, citation accuracy usually drops.

Read
Guide8 min read

Collapsible methodology and AI retrieval

AI assistants can retrieve facts from pages with collapsible methodology sections when the content exists in the HTML and the main claim stands on its own. If your caveats, definitions, or sampling notes only appear after interaction, citation accuracy gets worse fast.

Read
Guide8 min read

Publish llms.txt Without Public Docs?

If your site has no public docs, llms.txt is rarely an AI visibility lever. It can still help internal governance, but only if you treat it as documentation, not ranking strategy.

Read
Guide10 min read

Keep old screenshots on one page?

You can keep current and historical screenshots together, but only when the page labels them hard enough that an AI assistant does not quote an outdated interface as present truth. If your page mixes eras casually, split it.

Read
Guide9 min read

Do repeated summaries compete?

Repeated summaries help scanning, but they often create extraction conflicts when each section restates the answer with slightly different wording. The fix is not less clarity, it is one clearly dominant answer and subordinate summaries that point back to it.

Read
Guide8 min read

Move Caveats Out of Parentheses?

If a caveat changes the meaning of a claim, do not hide it in brackets. Put it in the main sentence, or AI assistants may quote the clean claim and drop the limit.

Read
Guide9 min read

AI fact retrieval from definition cards

AI assistants can retrieve facts from definition cards when the card exposes the term, definition, scope, and qualifiers in plain HTML. They fail when cards hide key caveats, rely on JavaScript, or split the answer across decorative UI.

Read
Guide8 min read

Put the answer in image alt text?

Do not hide your main answer in alt text and expect AI assistants to quote it reliably. Alt text is support copy, not a safe home for your canonical fact.

Read
Guide9 min read

Anchor linked glossaries and AI retrieval

Anchor linked glossaries can help AI assistants retrieve facts, but the anchor links themselves are not the win. The real win is whether each definition is present in plain HTML, clearly labeled, and supported by surrounding page context.

Read
Guide8 min read

Glossary Terms in Tables, Good or Bad?

Glossary definitions inside tables help when the reader already knows the frame. They confuse extraction when the table is doing too many jobs at once, especially definition, comparison, caveat, and example together.

Read
Guide8 min read

Repeated summary boxes and AI fact retrieval

AI assistants can retrieve facts from repeated summary boxes, but duplicated summaries often compete with the main source wording. If the boxes drift, oversimplify, or drop qualifiers, citation quality gets worse.

Read
Guide8 min read

Two column layouts and AI fact extraction

Two column comparison layouts can work for AI extraction, but they fail fast when labels, qualifiers, or verdicts are visually clear and structurally weak. The fix is not fancy schema. It is cleaner HTML, tighter pairing of claims and caveats, and fewer layout tricks.

Read
Guide8 min read

Use Version Labels on Fast-Changing Pages?

Usually yes, if the page changes often and old wording can linger in AI answers. Version labels help separate current statements from superseded ones, but they only work when the page structure stays simple and the labels are visible near the claim itself.

Read
Guide9 min read

Keep key facts out of carousels?

Yes, in most cases. Server rendering makes carousel text fetchable, but it still makes facts easier to miss, detach from qualifiers, or lose among repeated UI chrome.

Read
Guide9 min read

Split Guidance From Implementation Notes?

Split current guidance from implementation notes when the recommendation changes faster than the underlying setup details, or when mixed timelines cause citation mistakes. The goal is simpler retrieval, cleaner recency, and fewer stale AI answers.

Read
Guide8 min read

Do Breadcrumb Labels Help AI Focus?

Breadcrumb labels can reinforce page topic and hierarchy, but they rarely fix a weak page. They help most when the main heading, URL, title, and visible facts already agree.

Read
Guide8 min read

Duplicated desktop modules and AI facts

AI assistants can usually retrieve facts from pages that duplicate desktop modules, but repeated or conflicting copy increases the odds of bad extraction. The fix is not cosmetic deduplication, it is choosing one canonical wording for each fact and keeping variants aligned.

Read
Guide8 min read

AI facts from sortable tables?

AI assistants can retrieve facts from sortable tables when the underlying table is present in server delivered HTML. They fail more often when sorting rewrites cells, hides qualifiers, or depends on JavaScript state.

Read
Guide8 min read

Qualifiers in table cells or below?

If a qualifier changes the meaning of a table entry, keep it inside the same cell. Notes below tables are useful for context, but they are a weak place to park facts you need AI assistants to retain.

Read
Guide9 min read

Current vs proposed plans on one page

AI assistants can retrieve facts from mixed current and proposed plan pages, but they often detach timing from the claim. If your live policy and future plan sit together without hard labels, expect bad summaries.

Read
Guide8 min read

Move key definitions out of sidebars?

Move key definitions out of sidebars when the term is essential to the page's main claim, comparison, or recommendation. If the definition matters for citation accuracy, put it in the main body near the first use.

Read
Guide8 min read

Do Legal Footers Hurt AI Extraction?

Legal footers rarely break AI visibility on their own. They become a problem when repeated compliance text is longer, more prominent, or more structurally consistent than the answer you want assistants to extract.

Read
Guide8 min read

Repeat entity names after pronouns?

If a page matters as a source document, restating the full entity name after a few pronouns usually improves extraction. Do it for clarity, not keyword stuffing, and stop before the copy turns robotic.

Read
Guide9 min read

Label examples to prevent AI citation errors?

Yes, if a page mixes rules, claims, and illustrations, label examples explicitly. Clear example labels reduce the odds that AI assistants quote an illustration as if it were your actual policy or fact.

Read
Guide8 min read

Facts Hidden in Testimonial Carousels

If your strongest proof points live only inside testimonial sliders, AI assistants often fail to retrieve them cleanly. The fix is not removing testimonials, it is moving the canonical fact into stable visible copy first.

Read
Guide9 min read

Separate methodology and findings pages?

Separate methodology and findings pages help when your evidence needs clean extraction and your caveats are getting stripped from the result. They hurt when the split forces users and crawlers to stitch basic context back together.

Read
Guide9 min read

AI retrieval from table notes

AI assistants can miss, detach, or flatten notes attached to comparison tables. If a qualifier matters, repeat it in visible body copy near the claim instead of trusting the note alone.

Read
Guide8 min read

Put source dates in tables or below?

Usually, put source dates inside the table when recency changes the meaning of a row. Put them below only when one date applies to the whole table and repeating it would add noise.

Read
Guide9 min read

Facts Hidden in Calculator Output

If your best facts appear only after a user interacts with a calculator, AI systems often fail to retrieve them. The fix is usually simple, publish the same facts in stable HTML with qualifiers attached.

Read
Guide9 min read

Split long service pages for AI?

Split a long service page when the commercial pitch keeps colliding with facts AI assistants need to extract cleanly. Do it when accuracy, qualifiers, and stable claims matter more than keeping everything on one URL.

Read
Guide9 min read

Duplicated Mobile Content and AI Facts

Duplicated mobile content does not automatically block AI fact retrieval. It becomes a problem when mobile and desktop variants split, hide, or contradict the canonical answer.

Read
Guide8 min read

Restate entity names near key facts?

If a page carries multiple subjects, restating the entity name near the claim usually reduces attribution errors in AI answers. It is a small formatting move, not a magic ranking lever, and it matters most on dense pages with comparisons, aliases, or repeated pronouns.

Read
Guide9 min read

When page summaries flatten qualified claims

If your summary strips away qualifiers, AI assistants often repeat the cleaner but less accurate version. The fix is structural, not stylistic, keep claims and caveats physically attached.

Read
Guide9 min read

Repeated Nav Labels and Page Focus

Repeated navigation labels rarely hurt on their own. They become a problem when global template text, repeated anchors, and category names drown out the page's actual answer and make extraction messy.

Read
Guide9 min read

Examples vs rules on one page

AI assistants often blur examples into rules when pages mix policy, guidance, and illustration in one flow. The fix is not magic schema. It is explicit labeling, tight structure, and repeating the rule where the example appears.

Read
Guide9 min read

Embedded Widgets and AI Citations

If key facts exist only inside third party embeds, AI assistants often cannot extract them reliably. The safer pattern is to publish the same facts in plain HTML on your own page.

Read
Guide9 min read

Inline Definitions or Glossary Links?

If you want AI assistants to quote the right meaning, put the definition where the claim is used. Separate glossary pages still help, but they should reinforce the canonical wording, not replace it.

Read
Guide8 min read

Put conclusions before evidence?

Lead with the answer, then support it. On pages meant to be cited by AI assistants, conclusions placed before evidence are easier to extract, less likely to be mangled, and faster to verify.

Read
Guide8 min read

Can AI Read HTML Data Tables Correctly?

AI assistants can often pull facts from HTML tables, but accuracy drops when headers are vague, cells carry qualifiers elsewhere, or the table is interactive. Treat tables as structured evidence, not as a place to hide context.

Read
Guide8 min read

Repeated CTAs and AI fact retrieval

AI assistants can still retrieve facts from pages packed with repeated CTA blocks, but repetition often weakens extractability by diluting the main answer. The fix is not removing CTAs entirely, it is making facts more structurally obvious than the sales layer.

Read
Guide8 min read

When Schema Conflicts With Page Copy

Schema helps only when it clarifies what the page already says. When structured fields and visible copy disagree, extraction gets messier, trust drops, and assistants may quote the wrong version.

Read
Guide8 min read

When intros over qualify the answer

If your intro spends more time hedging than answering, AI assistants often miss the usable fact. The fix is not less nuance, it is better placement of nuance.

Read
Guide8 min read

Keep key facts out of expandable FAQs?

Usually yes. If a fact matters for AI retrieval and citation accuracy, put it in visible body copy first, then repeat it inside an FAQ if that helps humans.

Read
Guide9 min read

Superscript Markers and AI Extraction

Superscript reference markers do not reliably preserve meaning for AI assistants. If the qualifier, source, or exception lives only in the marker trail, expect dropped context and sloppy citations.

Read
Guide9 min read

Separate URLs for facts and examples?

Use separate URLs for facts and examples when your canonical claims need to stay stable, quotable, and easy for AI systems to extract. Keep them together when the example is required to interpret the fact correctly.

Read
Guide9 min read

AI citations to redirected URLs

A redirected URL can still pass a user to the right place, but AI citations often get weaker when the cited page moves, chains, or collapses into a broader destination.

Read
Guide8 min read

Definitions Before Comparisons?

On pages that need to define a term and compare options, lead with a tight definition only if it helps the comparison read cleanly. If the definition becomes a mini glossary, it will steal attention and weaken extractability.

Read
Guide9 min read

Duplicate chart facts in body copy?

Yes. If a chart contains a fact you want cited, restate that fact in plain body copy near the chart. Do not make the reader or the crawler infer the takeaway from visuals alone.

Read
Guide9 min read

When Glossary Pages Compete With Guides

Glossary pages start competing with guides when both pages expose the same clean definition, examples, and qualifiers in similar wording. If you do not assign distinct jobs, AI assistants and search systems can split citations across both.

Read
Guide8 min read

Can AI read HTML table footnotes?

AI assistants can retrieve facts from HTML table footnotes, but they often separate the main value from the qualifier that makes it true. If the footnote changes the meaning, do not leave it trapped below the table.

Read
Guide9 min read

Plain summaries beside technical content?

Plain language summaries can improve AI extractability and human comprehension, but only when they stay faithful to the technical source. If the summary drifts, you create citation risk instead of clarity.

Read
Guide9 min read

Nested lists and AI fact extraction

AI assistants can often pull facts from nested lists, but accuracy falls when the parent child relationship holds the real qualifier. If the nesting changes meaning, put the full fact in a standalone sentence too.

Read
Guide9 min read

Split tables into fact pages?

Comparison tables are good for side by side decisions, but they often compress qualifiers so hard that AI assistants quote them badly. Split them into separate fact pages when accuracy, caveats, and canonical retrieval matter more than convenience.

Read
Guide9 min read

Mix facts and opinions on one page?

A mixed page can rank, convert, and even earn citations. It also makes extraction harder when hard facts, verdicts, caveats, and persuasion copy are packed into the same block.

Read
Guide9 min read

Use last reviewed dates with publish dates?

Yes, if the page contains facts that can age. Publish dates tell when the page started, last reviewed dates tell readers and AI systems the facts were checked again.

Read
Guide8 min read

Sticky Table Headers and AI Retrieval

Usually yes, if the sticky header is only visual and the underlying table remains normal HTML. Problems start when the sticky behavior rewrites the table, duplicates headers, or hides cells behind JavaScript-heavy components.

Read
Guide9 min read

Do AI assistants read captions correctly?

AI assistants can read HTML captions and figure text, but they often separate the visual from the qualifier. Put critical facts in body copy first, then use captions as support.

Read
Guide9 min read

Repeated Disclaimers on Every Page

Repeated disclaimers rarely create a penalty by themselves, but they can dilute the answer signal on a page. If the boilerplate is longer, louder, or closer to the core claim than the actual fact, AI systems have more noise to sort through.

Read
Guide9 min read

Turn resource pages into HTML for AI?

If a key resource only lives as a downloadable file, AI assistants are less likely to quote it cleanly. Publish an HTML version for retrieval, keep the file for utility, and make one page the canonical fact source.

Read
Guide9 min read

Source links next to claims or below?

If you want cleaner AI extraction and fewer detached claims, place the source link close to the statement it supports. Put grouped sources below only when the section is interpretive, long form, or source dense.

Read
Guide9 min read

One page, many questions, what happens?

One page can rank for a cluster of related AI retrieval intents, but only if the page keeps each answer distinct, scoped, and easy to extract. When it turns into a mixed FAQ blob, citation quality drops.

Read
Guide10 min read

Can AI cite glossary side panels?

AI assistants can sometimes pull facts from glossary side panels, but they often detach definitions from qualifiers, scope notes, and source context. If the fact matters, put the canonical version in the main body too.

Read
Guide9 min read

Trust badges vs AI answer extraction

Repeated trust badges can crowd out the facts AI systems need to quote. They help persuasion for human buyers, but they often weaken extractability when they interrupt or duplicate the answer.

Read
Guide8 min read

Units and qualifiers in one sentence?

Put the unit, scope, time condition, and exception in the same sentence as the claim. If you split them apart, AI systems often keep the headline fact and drop the constraint.

Read
Guide8 min read

Can AI Read Facts From Comparison Cards?

AI assistants can pull facts from comparison cards when the content is present in the initial HTML, clearly labeled, and not hidden behind UI logic. If the cards rely on JavaScript, hover states, or inconsistent labels, extraction gets shaky fast.

Read
Guide8 min read

Key facts hidden in hover states

If a critical fact only appears on hover, many AI crawlers and assistants will not extract it reliably. Put claimable facts in visible HTML first, then use hover for decoration or secondary detail.

Read
Guide8 min read

Should cited claims name sources in copy?

If you want AI assistants to preserve attribution and context, naming the source near the claim usually helps. Doing it everywhere can make pages unreadable, repetitive, and weaker as persuasion.

Read
Guide8 min read

AI retrieval from HTML definition terms

AI assistants can usually pull facts from HTML definition terms when the structure is simple and the qualifier stays attached to the claim. The pattern fails when teams use definition lists as a visual trick instead of a factual one.

Read
Guide9 min read

Should AI citation copy use blockquotes?

Blockquotes can help when you are reproducing a source or isolating a precise statement, but they are not a reliable citation hack. For most pages, cleaner body copy, tighter qualifiers, and better page structure do more for AI extraction.

Read
Guide9 min read

Template Injection vs AI Extraction

Related content modules often hurt AI extraction when they interrupt the answer, duplicate nearby entities, or push qualifiers away from the main claim. The fix is usually structural, not cosmetic.

Read
Guide8 min read

Keep caveats attached in AI answers

If a caveat sits far from the main claim, assistants often drop it in summaries. Write the caveat as part of the claim, repeat it in the proof section, and avoid layouts that split the two apart.

Read
Guide8 min read

Do jump links help AI crawlers?

Jump links can improve navigation and make answer sections easier for humans to reach. They do not fix weak page structure, hidden content, or JavaScript rendering problems on their own.

Read
Guide8 min read

Current vs archived facts pages

If a page mixes live facts with retired policies, old specs, or superseded statements, AI assistants can quote the wrong thing. Separate pages usually reduce citation errors, but only when the current page is clearly canonical and the archive is unmistakably historical.

Read
Guide9 min read

Format Dates So AI Reads Recency

AI assistants often miss recency when dates are ambiguous, duplicated, or detached from the claim they qualify. Clear visible dates, one canonical current version, and consistent machine readable markup reduce that risk.

Read
Guide9 min read

Can AI cite story-led pages?

AI assistants can cite story-led pages, but storytelling often buries the quotable fact, qualifier, or definition the model needs. If the answer is not easy to extract, the page may still rank with humans and still lose citations.

Read
Guide9 min read

Facts Hidden in Comparison Filters

If your decisive facts live only inside comparison filters, many AI systems will not retrieve them reliably. Put the same facts in crawlable, visible page copy or expect citation gaps and wrong summaries.

Read
Guide9 min read

One URL for each claimable fact?

If the same claimable fact appears across many URLs, AI assistants and crawlers get more chances to pick the wrong version. A single canonical source usually improves consistency, but some facts need controlled repetition.

Read
Guide9 min read

Can AI retrieve facts from definition tables?

Yes, often better than from dense prose, if the table uses plain labels, stable terms, and visible qualifiers. The failure mode is not the table itself, it is ambiguous headings, merged concepts, and missing context.

Read
Guide9 min read

Methodology Sections AI Can Quote

If you want AI assistants to quote your methodology accurately, make the method extractable, bounded, and separate from interpretation. Most errors come from mixed claims, hidden qualifiers, and scattered definitions.

Read
Guide8 min read

Same Answer in Schema and Copy?

If a fact matters, publish it in visible copy first and mirror it in schema only when the schema adds structure. Do not let schema carry claims your page body does not state plainly.

Read
Guide8 min read

Do sidebars help AI extraction?

Sidebars and callouts can improve AI extractability when they restate a single fact cleanly. They hurt when they introduce competing claims, vague summaries, or repetitive noise around the answer.

Read
Guide9 min read

Publish source excerpts for AI citations?

Yes, usually. Pairing short source excerpts with your interpretation makes factual claims easier to verify, quote, and cite, as long as you separate what the source says from what you think it means.

Read
Guide8 min read

Format Abbreviations for AI Retrieval

If you want AI assistants to retrieve the right concept, put the expanded term and abbreviation together in visible copy, then repeat the preferred form consistently. The goal is not style purity, it is reducing ambiguity at extraction time.

Read
Guide8 min read

AI and archived policy pages

Sometimes, but not reliably enough to trust by default. If your current and archived policy pages look too similar, assistants can quote the wrong version or blend both.

Read
Guide9 min read

Repeat facts in intro and detail?

If a fact matters for AI retrieval and human comprehension, state it once high on the page and again where you explain it. The win is clarity and qualifier control, not keyword density.

Read
Guide9 min read

Do definition lists help AI retrieve facts?

Definition lists can help AI assistants extract paired facts, but only when the HTML is clean and the surrounding page removes ambiguity. They are a formatting aid, not a reliability guarantee.

Read
Guide9 min read

Keep qualifiers next to claims

If the condition, exception, or scope note sits far from the headline claim, AI assistants often lift the simple version and drop the limit. Put the qualifier beside the claim if you want cleaner summaries and fewer misquotes.

Read
Guide8 min read

Comparison Verdicts AI Can Extract

Your verdict should be explicit, segmented by use case, and easy to quote in one pass. The goal is not clever copy, it is a clean answer an assistant can lift without mislabeling the winner.

Read
Guide9 min read

Infinite Scroll and AI Citation Accuracy

Usually not reliably. Infinite scroll often hides source text behind client side loading, weak URLs, and unstable page boundaries, which makes extraction and citation less precise.

Read
Guide8 min read

Put the answer first for AI citation?

If you want AI assistants to quote your page cleanly, lead with the answer in plain language. Then support it immediately with scope, evidence, and caveats so the summary does not drift.

Read
Guide9 min read

Do Templates Dilute AI Extraction?

Repeated template copy does not automatically kill AI visibility, but it can make page specific facts harder to isolate. On large sites, the real risk is weak information hierarchy, not reuse by itself.

Read
Guide8 min read

Use HTML Lists for AI Retrieval?

HTML lists help AI systems pull steps, criteria, and grouped facts with less ambiguity than dense paragraphs. They are not a universal upgrade, and overusing them can strip context the model needs to answer well.

Read
Guide8 min read

Should You Add Summary Boxes for AI?

Summary boxes can help AI assistants lift the right facts faster, but only when the page beneath them is consistent, crawlable, and worth citing on its own.

Read
Guide8 min read

Handling disputed facts for AI citations

If a fact is contested, do not hide the dispute. Label the claim, name the source, state the counterclaim, and separate settled facts from interpretation so AI assistants have something clean to quote.

Read
Guide8 min read

Why AI assistants pick one source page

AI assistants usually prefer the page that is easiest to fetch, parse, reconcile, and quote without adding interpretation risk. That is rarely the prettiest page, and often the most explicit one.

Read
Guide9 min read

Can AI Extract Facts From Comparison Tables?

AI assistants can often pull facts from comparison tables, but reliability drops when headers are vague, cells cram multiple claims, or key caveats live outside the table. The best tables are boring, explicit, and backed by visible prose nearby.

Read
Guide9 min read

Hidden text and AI assistants

AI assistants can sometimes retrieve hidden text, but they do it less reliably than plain visible body copy. If a fact matters for citation, put it in the HTML of the page and make it easy to quote without interaction.

Read
Guide9 min read

Put dates near claims you want cited?

Placing a publish or updated date near a claim can help an AI assistant keep time-sensitive facts attached to the statement. It does not rescue weak pages, unclear sourcing, or client-side rendering.

Read
Guide9 min read

Format Definitions for AI Retrieval

If you want service pages cited by AI assistants, definitions need to be explicit, local to the claim, and written in plain language. The win is cleaner extraction, not prettier copy.

Read
Guide9 min read

Image Text or Body Copy for Key Facts?

If a fact matters for AI retrieval, search visibility, or clean citation, it should live in plain body copy. Image text can reinforce a point, but it should not be the only place the fact exists.

Read
Guide9 min read

Same Fact on Multiple Domains

When the same claim appears on your site, partner sites, directories, and copied pages, AI assistants do not reliably reward the original source. They usually pick the clearest, most retrievable, and most corroborated version.

Read
Guide8 min read

Separate Opinions From Facts for AI Citation?

If you want AI assistants to quote you accurately, separate stable facts from interpretation. The goal is cleaner extraction, not sterile writing.

Read
Guide8 min read

When Footnotes Help AI Extraction

Footnotes help when they verify a nearby claim without breaking the sentence that carries the fact. They distract when they become a second layer of copy, push key facts away, or force crawlers and models to reconstruct meaning across fragments.

Read
Guide8 min read

AI fact retrieval on translated pages

Yes, sometimes, but translated pages often break fact retrieval when meaning drifts, canonicals point wrong, or key facts exist in only one language. If you want AI assistants to quote the right version, translation workflow matters as much as SEO.

Read
Guide9 min read

Do canonicals affect AI citations?

Canonicals can help AI assistants converge on one source, but they do not rescue weak page structure, conflicting facts, or hidden content. Treat them as a cleanup signal, not a citation strategy by themselves.

Read
Guide9 min read

Quote-ready blocks for AI citations?

Quote ready blocks can reduce misquotes and make facts easier for AI assistants to lift cleanly. They do not create authority on their own, and they can make pages worse if overused.

Read
Guide9 min read

Tabs and accordions for AI facts?

AI assistants can often extract facts from tabs and accordions if the content is present in the initial HTML. Reliability drops fast when key copy is injected with JavaScript, gated behind events, or fragmented across UI states.

Read
Guide9 min read

What to Put in Page Intros for AI Answers

Page intros help AI answers when they state the core fact fast, define the subject clearly, and remove throat clearing. The intro is not magic, but it often decides whether your page gets extracted cleanly or skipped.

Read
Guide8 min read

Category pages for AI citations

Category pages can earn AI citations, but only when they do more than list links. The page needs a clear claim, stable facts, and visible structure that a crawler can extract without guessing.

Read
Guide8 min read

Design Author Pages for AI Trust

Author pages help AI systems and human reviewers connect claims to a real operator. The win is not decoration, it is making expertise, accountability, and evidence easier to extract.

Read
Guide9 min read

Pagination and facets vs AI crawlers

Pagination and faceted navigation often create too many near-duplicate URLs, weak canonical signals, and fragmented facts. AI crawlers then fetch the wrong pages, miss the core page, or quote filtered variants that were never meant to stand alone.

Read
Guide9 min read

Consolidate Pages for Cleaner AI Citations

Consolidate overlapping pages when multiple URLs state the same core facts with small wording differences. AI systems handle that sprawl badly, especially when they need one stable page to quote or summarize.

Read
Guide8 min read

Publish Research if AI Strips Context?

Yes, but publish it in a format that survives extraction. If your research only works when read end to end, AI summaries will flatten it, and your citations will be weak or misleading.

Read
Guide9 min read

Can comparison pages win AI citations?

Yes, if the page behaves like a decision document instead of a sales page. The trick is to make trade offs, scope, and evidence extractable in plain language.

Read
Guide9 min read

AI-Retrievable Definition Pages

A definition page gets retrieved when the answer is obvious in visible HTML, tightly scoped, and supported by surrounding context. Most pages fail because they mix glossary intent with sales copy, hide facts in tabs, or rely on JavaScript rendering.

Read
Guide9 min read

Above the Fold for AI Extraction?

Sometimes, but not for the reason most teams think. Put core facts early because it improves extraction reliability and editorial clarity, not because AI sees a screen like a human.

Read
Guide8 min read

PDFs vs HTML for AI Citation

PDFs can be cited by AI systems, but equivalent HTML usually gives you better control, cleaner extraction, and fewer formatting failures. PDFs work best as supporting assets, not as the only canonical source for core claims.

Read
Guide9 min read

AI site architecture for canonical facts

AI assistants find canonical facts faster when your site gives each important claim one clear home, repeats it consistently, and removes routing and rendering ambiguity.

Read
Guide8 min read

How to cite sources so AI trusts your page

AI systems trust pages that show where facts came from, separate sourced claims from opinion, and keep citations close to the statement being made. The goal is not academic style. It is fast verification.

Read
Guide8 min read

When Schema Helps, When Copy Is Enough

Schema helps when it removes ambiguity from facts machines struggle to connect reliably. If the page already states a simple claim clearly in visible copy, schema usually supports it rather than rescuing it.

Read
Guide8 min read

Can pSEO Pages Earn AI Citations?

Programmatic SEO pages can earn AI citations, but only when each page carries extractable, page-specific facts. Thin template fleets usually get summarized away or skipped.

Read
Guide8 min read

Glossary Pages for AI Retrieval

Design glossary pages as extractable fact pages, not thin SEO stubs. Clear definitions, stable wording, explicit context, and server rendered content matter more than clever templates.

Read
Guide9 min read

What to Remove for Better AI Extraction

If AI assistants keep missing or mangling your facts, the fix is often removal, not addition. Strip out layout patterns, copy habits, and rendering choices that hide extractable claims.

Read
Guide8 min read

Do updates change AI citations?

Updating a source page can improve how AI assistants cite it, but not on your schedule. The real issue is whether crawlers can access the page, extract the changed fact cleanly, and trust it over competing sources.

Read
Guide8 min read

Conflicting facts and AI answers

AI assistants usually do not reconcile contradictions the way an editor would. They extract the clearest, most repeated, most accessible claim, then answer with that version.

Read
Guide9 min read

When Tables Help AI Extractability

Use tables when the reader, and the model, need stable comparisons, specs, eligibility rules, or timelines at a glance. Do not force narrative into tables, because rigid structure can hide context and create bad summaries.

Read
Guide9 min read

What makes pages easy to cite

AI assistants cite pages that expose clear facts, stable wording, and obvious attribution in HTML. If a model has to infer, chase context, or wait for JavaScript, your page becomes harder to quote.

Read
Guide8 min read

Split facts and narrative onto separate pages?

Most teams do not need separate fact pages and story pages. They need one page that makes extractable facts obvious, while keeping narrative close enough to preserve meaning and trust.

Read
Guide9 min read

When AI Search Fails Low Authority Sites

AI search optimization can help low authority sites get quoted, but it fails when the page is hard to extract, easy to doubt, or unsupported by outside references. Clean structure matters, yet citation eligibility is not the same as citation likelihood.

Read
Guide8 min read

Write Copy That Survives AI Summaries

Write for extraction, not just persuasion. The copy that survives AI summarization puts claims in plain language, keeps context close to facts, and removes ambiguity that models compress badly.

Read
Guide8 min read

What Breaks AI Citation on JS-Heavy Sites

AI citation often fails on modern marketing sites because the page looks complete in a browser but incomplete to crawlers. If key facts arrive late, hide in tabs, or depend on hydration, assistants have less to quote and less confidence to cite.

Read
Guide9 min read

Block AI Crawlers on Staging?

Yes, you should block AI crawlers on staging and test environments by default. Use auth, noindex, and per bot robots rules so unfinished pages do not get fetched, quoted, or confused with production.

Read
Guide8 min read

Schema that helps after FAQ rich results

FAQ rich results are gone, but that does not make schema irrelevant. The useful types now are the ones that reduce ambiguity for crawlers and answer systems extracting facts from your pages.

Read
Guide9 min read

Measure AI Visibility Without Screenshots

You can measure AI visibility without trusting vendor dashboards by combining prompt tracking, server logs, rendered-page checks, and citation capture. The point is not a single score, it is a repeatable evidence trail that shows what models can access, extract, and cite.

Read
Guide8 min read

Structure Pages for AI Fact Extraction

If you want AI assistants to quote your site, structure pages for extractability first. Clear assertions, stable labels, server rendered content, and tight evidence formatting beat decorative UX.

Read
Guide9 min read

Why AI cites aggregators first

AI assistants often cite aggregators because those pages are easier to crawl, compare, and quote than vendor pages. The fix is usually extractability, corroboration, and page design, not louder publishing.

Read
Guide8 min read

What llms.txt Still Does

llms.txt is not a ranking or citation lever for Google Search. It can still help with documentation hygiene, internal alignment, and giving AI vendors a clean map of what you want quoted.

Read
Guide8 min read

Do AI Crawlers Run JavaScript?

Short answer, treat AI crawlers as fetchers, not browsers. If critical copy, entities, and citations depend on client-side rendering, many AI systems will miss them.

Read
Guide8 min read

Should You Publish llms.txt?

Publish llms.txt only as a low effort housekeeping file, not as an AI visibility strategy. It does not improve Google Search performance, and current evidence does not show citation lift.

Read
Comparison10 min read

AI visibility tools compared honestly

AI visibility tools are useful for spotting trends, but none can directly measure how often your brand is truly seen, trusted, and cited by AI assistants. The right choice depends on whether you need prompt tracking, source analysis, or technical debugging.

Read
Guide8 min read

IndexNow for AI freshness

IndexNow can speed up URL discovery inside Microsoft's ecosystem, but it is not a direct citation switch for AI assistants. Use it to reduce lag after meaningful page changes, not as a substitute for extractable pages and clear entities.

Read
Guide9 min read

Why vendor sites lose AI citations

Vendor sites often lose broad commercial AI citations because assistants prefer pages that compare, define, and quote cleanly without obvious sales intent. If you want to win more of those mentions, you need extractable evidence pages, not just product pages.

Read
Guide9 min read

AI answer schema, signal or folklore?

Most schema advice for AI answers mixes solid extraction help with wishful thinking. Here is what actually improves machine readability, what does not, and where the advice breaks.

Read
Guide8 min read

Why chatbots misdescribe your brand

Chatbots usually misdescribe brands when your site, profiles, and third party mentions disagree on basics like category, audience, and product scope. Entity consistency reduces that drift by making the same facts easy to extract, repeat, and cite.

Read
Guide8 min read

Bing AI grounding queries guide

The Bing AI performance report is useful because grounding queries show how Microsoft systems connect prompts to pages. Treat it as directional editorial input, not a clean attribution model.

Read
Field note8 min read

Do AI Crawlers Respect robots.txt?

Some AI crawlers clearly check robots.txt and change behavior when blocked. Others are noisier, less transparent, or hard to attribute cleanly from logs alone, so the practical answer is bot specific, not universal.

Read
Guide9 min read

SSR vs CSR for AI citations

If AI crawlers cannot extract the page without running JavaScript, your citation odds drop fast. Server rendered HTML gives assistants usable text at fetch time, which is often the deciding difference.

Read
Guide8 min read

Test What AI Can Quote From Your Page

If an AI assistant cannot lift a clean fact, definition, step, or comparison from your page, it is unlikely to cite you reliably. This guide shows how to test quote readiness with a repeatable operator workflow.

Read
Field note9 min read

What GPTBot Fetches, From Server Logs

If you want AI visibility work to hold up, stop guessing from page source and check server logs. GPTBot mostly tells you whether core HTML, assets, and crawl access are usable, not whether your JavaScript app magically rendered for it.

Read
Rendering11 min read

Can AI Crawlers Read Your Site? The Rendering Problem

No, the major AI crawlers do not execute JavaScript. They read whatever HTML arrives in the first response and nothing else, which means a client rendered site hands them an empty container. We fetched our own routes with the documented GPTBot string and published the byte counts, including the ones that embarrassed us.

Read
Crawler access9 min read

AI Crawler Access: robots.txt for GPTBot and Friends

Training crawlers and search crawlers are different machines with different consequences, and one robots.txt line written by someone who did not know that can remove you from AI answers entirely. Every documented agent string, what it is for, and the specific cost of denying each one.

Read
Citation mechanics12 min read

AI Cites Passages, Not Pages: What Gets You Quoted

Retrieval scores passages rather than pages, which is why a narrow self contained section can enter an answer the whole page would never have ranked for. The traits that separate a quoted passage from an ignored one, the five tests we run before publishing, and the widely repeated citation statistics we refuse to print.

Read
Method11 min read

GEO vs SEO: Mostly the Same, Two Things Genuinely New

Mostly the same discipline, and Google says so in its own documentation. Two differences are genuinely new: the AI crawlers do not run JavaScript while Googlebot does, so a site can pass classic SEO and fail retrieval outright, and retrieval scores passages instead of pages. Everything else being sold as new is not.

Read
Schema10 min read

Schema for AI Answer Engines: What Still Earns Its Keep

Google states plainly that structured data is not required for its generative features. Microsoft has said on the record that schema helps its models understand content. Both are true at once, and the reason to ship it is entity disambiguation rather than a ranking effect. Which types still pay for themselves, and which are dead.

Read
Entities11 min read

AI Describes Your Company Wrong Because Sources Disagree

An assistant is not reading your about page and getting it wrong. It is reconciling sources that disagree with each other, and the loudest disagreement wins. The five step correction loop we run, starting with the part most teams skip: finding out which sources the model is actually reconciling.

Read
Measurement9 min read

Measuring AI Search Visibility: What Is Actually Knowable

Two free first party reports exist and almost nobody has switched them on. For the assistants that report nothing at all, the honest instrument is a fixed query panel run the same way every month. Also why referral traffic undercounts, and why a single composite visibility score cannot move for a reason you can act on.

Read
Benchmark12 min read

AI Crawlers Get an Empty Page: The Extractability Index

A page is invisible to an AI crawler when the first response carries no body copy, which is measurable in bytes rather than arguable. The method, the shell baseline measured on the same domain the same day, and the raw counts for every route type we fetched with the documented GPTBot string.

Read
Methodology9 min read

Results and Methodology: What We Can Actually Prove

Every number this site publishes, what instrument produced it, what it does not cover, and where we have no data at all. The failing rows from our own audit are left in, because a results page with no failures in it is a marketing page wearing a lab coat.

Read
Evidence8 min read

The Evidence Register: Every Claim, Labelled and Dated

The table every other page here defers to. Each load bearing claim appears once with a confidence label, its source, the date it was last verified and the date it stops being trusted. Rows are ordered by recheck date, soonest first, so the claim closest to expiry is the first one you read.

Read
Evidence16 min read

Outbound Pros, Graded Against Our Own Evidence Rules

InboundPros and Outbound Pros are the same group, so recommending the agency without applying our own labels to it would make the labels decorative. Here is the group agency run through the same confidence rules as everyone else, including the claims we will not stand behind and the buyers it fits badly.

Read

Talk through your AI visibility with people who measure it

30 minutes. We will look at what assistants can actually retrieve from your site and tell you plainly what is worth fixing first.

Book a strategy call

30 minutes, no obligation. The calendar shows real availability.

Or start with the free GTM audit from Outbound Pros