AI citations: how to back your pages with sources, dates and corrections

What an AI citation is, and what it proves

An AI citation is a link, shown with an AI answer, to a page the answer claims to rest on. Every product describes it a little differently. Google's guide to optimising for generative AI search says AI Overviews and AI Mode retrieve pages from the Search index and show "prominent, clickable links to relevant web pages that support the information in the response." OpenAI's help centre says ChatGPT answers that use web search may include citations, and a Sources button, when available, lists cited sources and other relevant links. Perplexity's help centre says each answer includes numbered citations linking to the original sources.

Anthropic's documentation for developers is more specific. Each Claude web search citation carries the page's URL, its title and up to 150 characters of the text being cited. That's one sentence or less of your page doing the whole job of backing the answer.

A citation shows where an answer claims to come from. It doesn't prove the answer is right. Google's AI Overviews help page says AI Overviews "can and will make mistakes", and OpenAI's help centre says search results and citations can be incomplete, outdated or incorrect. Both ask people to check: OpenAI tells users to open a cited source, check that it supports the answer and review when it was published or updated, and Google says to check important information in more than one place. So the real test happens after the click, on your page.

A citation is also a different thing from a mention or a search ranking, and the three are easy to mix up in reports. The table sets them side by side; AI recommendations versus mentions goes further into the difference between being named and being suggested.

First check that the page can be cited at all

Evidence only helps a page an AI product is able to use. Google's AI features page says that to be eligible as a supporting link in AI Overviews or AI Mode, a page must be indexed and eligible to be shown in Google Search with a snippet. Google's guide to optimising for generative AI search adds a site-level step: a site must be included in Search generative AI features in Search Console to be eligible for display in those features.

AI answers don't only draw on the page that ranks first for the question someone typed. Google's guide defines query fan-out as a set of concurrent, related queries generated by the model to request more information and fetch additional relevant search results. Its example is a question about fixing a lawn full of weeds, which might fan out to searches such as "remove weeds without chemicals" and "how to prevent weeds in lawn". Google's AI features page says both AI Overviews and AI Mode may use the technique.

For a local business, that means a page answering one narrower question well, with its evidence on show, has a reason to be retrieved even when it isn't the strongest page for the broad search. A page on whether a split system needs its own circuit, for example, could support part of an answer to a broader question about installing air conditioning. No one can promise it will be picked. The point is that the work in this guide is worth doing on modest pages too, because a checkable answer to a narrow question is useful wherever it ends up.

Other products have their own gates. OpenAI's help article "Does ChatGPT tell the truth?" says the model may not be able to get information from a website because of technical issues, paywalls or preferences set in robots.txt. Crawler access for each product is covered in the AI visibility checklist, and why a crawl does not prove an AI citation explains what server logs can and can't tell you.

Snippet controls are the usual trap. They often go in for a sensible reason, such as keeping a staff list or an old notice out of results, and then stay on long after anyone remembers why. Google's robots meta tag documentation explains how each one reaches its AI features:

Put the source beside the claim, and open it yourself

Every fact you didn't create yourself should name its source in the same sentence, with a link. Google's link guidance says linking to other sites isn't something to be scared of, and that external links can help establish trustworthiness, "for example, citing your sources".

Then check that the source exists and says what you claim. AI tools are handy for finding leads, but OpenAI's help article "Does ChatGPT tell the truth?" lists "fabricated quotes, studies, citations or references to non-existent sources" among the mistakes its model can make. Treat a link an assistant suggested as a lead to follow up: it becomes evidence once a person has opened the page and found the sentence that supports the claim.

One caution from Google's guide before you start rewriting. Google says there's no requirement to break content into tiny pieces for AI to understand it, and lists "chunking" among the tactics site owners can ignore for Google Search. The changes below are about making claims checkable for a person, not reshaping pages for a machine.

These habits make each source easy to use:

• Name the source in words. "The Queensland Building and Construction Commission says..." tells the reader something even if they never click.
• Link to the exact page that states the fact, not the organisation's home page.
• Open every link before you publish and find the sentence that backs your claim. If you can't find it, change the claim or remove it.
• Use link text that describes the destination. Google calls good anchor text descriptive, reasonably concise and relevant, and gives "Click here" and "Read more" as bad examples.
• Write each claim so it makes sense on its own. A reader who lands mid-page from a citation hasn't read the paragraph before, so words like "this" or "as above" leave them guessing.
• Keep the evidence in visible text. Google's AI features page recommends making sure important content is available in textual form, and its structured data guidelines say not to mark up content that isn't visible to readers. A licence number that only appears on a photo of your van, or a service area that only exists in a PDF, can't be quoted.

Show who stands behind the page, and when it was written

A reader deciding whether to trust a cited page looks for a person and a date. Google's guidance on helpful content asks whether it's self-evident to visitors who authored the content, whether pages carry a byline where one might be expected, and whether bylines lead to more information about the author. The same guidance asks if a page presents information in a way that makes you want to trust it, "such as clear sourcing, evidence of the expertise involved, background about the author or the site that publishes it", and says that of the qualities Google groups as E-E-A-T, trust is most important.

For a service business the author is often the owner or the licensed person who does the work. A short author block can carry most of the evidence for expertise:

• A byline naming the person who wrote or checked the page, linked to an about page that says what they do and how long they've done it.
• The licence or registration behind the advice, written as text with its number, where the work needs one, and a link to the regulator's public licence search if it offers one.
• A reviewer line when someone other than the writer checked the facts, such as "Reviewed by [name], licensed electrician".
• A plain note on how the page was made if AI tools helped draft it. Google's guidance on generative AI content says sharing how content was created can give readers more context.

Keep dates honest, and correct in the open

A date tells the reader whether the page still applies. Google's guidance on byline dates asks for a user-visible date, featured prominently and labelled with words like "Published" or "Last updated". It recommends structured data of a type such as Article, with datePublished and dateModified filled in, and says the visible and structured dates should match. It also says not to use future dates, or the date of an event the page describes. Structured data has a job here and little more: Google's guide to optimising for generative AI search says there's no special schema.org markup needed for its AI features.

Keep other dates on the page to a minimum. Google's byline guidance says that if you've followed its advice and incorrect dates are still being selected, consider removing some or all of the other dates on the page. That includes the date you last checked each source. Keep those in a review log that lists each link and the claim it supports; how to keep AI visibility content current covers that log and the review cycle behind it.

The updated date has to mean something. Google's helpful content guidance asks, "Are you changing the date of pages to make them seem fresh when the content has not substantially changed?" Change the date when a fact, rule, service area or recommendation on the page changes, and when you publish a correction. Leave it alone for a fixed typo.

When a page turns out to be wrong, fix it and say so. The Australian Press Council's general principles ask member publications to "provide a correction or other adequate remedial action if published material is significantly inaccurate or misleading." A plumber or a physio isn't bound by those principles, but the habit shows readers you check your own work.

A useful correction note is short. It says what the page said before, what it says now and why, and links to the source behind the new version. Put it at the foot of the page under a heading such as "What changed", link to it from the "Last updated" date, and replace it when the next correction comes, keeping the full history in your review log. Then add one line inviting readers to report an error, with a link to your contact page.

Say a plumbing business in Caloundra has a hot water page that mentions a government rebate, and the rebate program closes. The owner removes the rebate section, sets "Last updated" to the day of the edit, and the "What changed" note reads "Removed the rebate section because the program has closed", linked to the closure notice. Anyone arriving from an AI answer that still mentions the rebate can see what happened. Search Console's URL Inspection tool can then request a recrawl, though Google says crawling can take from a few days to a few weeks and that requesting one doesn't guarantee inclusion. Wrong details on other people's sites are a separate job, covered in AI source correction and retraction.

Worked example: an evidence pass on one service page

Say an electrician in Hervey Bay has a page on switchboard upgrades and wants it ready to be checked by anyone who arrives from an AI answer. The business is hypothetical, and the page has the problems most service pages have. Here's the pass, in the order that wastes the least effort:

1. List every outside fact. The page has four: a line on safety switch rules for rental homes, a line saying older ceramic fuses "must be replaced", a mention of "the wiring standard", and the phrase "fully licensed" with no number.
2. Source each one or change it. The owner finds the regulator's page that states the safety switch rule, rewrites the line to match its wording and links it in the same sentence. No rule says every ceramic fuse must go, so that line becomes the electrician's own advice, labelled as such. The standard gets its full name and number instead of "the wiring standard".
3. Put the licence on the page as text. The licence number goes into the author block, with a link to the regulator's public licence search so a reader can confirm it.
4. Open every link. Each one should land on the exact page, and the supporting sentence should be on it. One link goes to a home page, so the owner swaps it for the page that states the rule.
5. Rewrite passages that lean on context. "As above, it depends, so give us a call" becomes "Whether a switchboard needs replacing or only new safety switches depends on its age and condition, which we confirm on site before quoting." The new sentence makes sense to someone who reads nothing else, which matters when the passage has to fit in the excerpt of up to 150 characters that Claude's web search tool attaches to each citation, according to Anthropic's developer documentation.
6. Move facts out of images and files. The service area was only on a map image and the hours were only in a PDF flyer, so both become text on the page.
7. Check the dates. The visible "Published" and "Last updated" dates should match the Article markup, and stray dates in the footer and old notices come off.
8. Add the trust furniture. A byline linked to the about page, a reviewer line, an empty "What changed" slot ready for the next correction, and a line inviting readers to report an error.
9. Check eligibility last. The page has no noindex or nosnippet, no data-nosnippet around the facts, and the site is included in Search generative AI features in Search Console.

Off-site evidence, tracking citations, and what no one can promise

What other sites say about you counts as evidence too, but only when it's genuine. Google's guide to optimising for generative AI search says its AI features can show what's being said about products and services across the web, including in blogs, videos and forum discussions, and that seeking inauthentic "mentions" isn't as helpful as it might seem. The off-site job is accuracy: Google's Business Profile guidelines ask you to represent your business as it's consistently represented in the real world, with an accurate address or service area. Citations and business listing accuracy covers how to line up one master record across directories.

To see whether your pages are being cited, use a routine you can repeat. One round tells you little, so the value is in comparing like with like over time:

• Write a fixed set of questions customers actually ask, in their words, and keep the wording identical each round.
• Run them in the same AI products on a set day each month, and note whether you were signed in. OpenAI's help centre says approximate location and saved memories can change the search ChatGPT runs.
• Log the date, the question, whether your site was linked, which page, and which other site was linked instead.
• Check Google's side in Search Console. Google's AI features page says appearances in AI features are counted in the Performance report under the Web search type, and its July 2026 optimisation guide points to a Generative AI performance report.
• Compare rounds only when they used the same questions and products; how to compare AI visibility reports explains why.