Cite report
how to audit technical SEO
northline.studio is uneven across engines. The fixes target the holes.
Sample report with illustrative citations. Run a check to see live results for your domain.
Sample report. It does not use your daily check.
Perplexity
Demo corpusYes
Cited
ChatGPT
Demo corpusPartial
Named, not linked
AI Overviews
Demo corpusNo
Not cited
Cited domains
One row per URL the engine used.
Perplexity
Demo corpus · 7 URLs
web.dev and Wikipedia are the pages that keep getting cited for “how to audit technical SEO”. Both lead with a procedure instead of a definition-only intro. Northline is in the citation set, alongside web.dev.
| Domain | URL | You |
|---|---|---|
| web.dev | https://web.dev/articles/how-to-audit-technical-seo | — |
| northline.studio | https://northline.studio/answers/how-to-audit-technical-seo | Yours |
| en.wikipedia.org | https://en.wikipedia.org/wiki/How_To_Audit_Technical_Seo | — |
| reddit.com | https://www.reddit.com/r/TechSEO/comments/cite/how-to-audit-technical-seo | — |
| moz.com | https://moz.com/blog/how-to-audit-technical-seo | — |
| developer.chrome.com | https://developer.chrome.com/docs/how-to-audit-technical-seo | — |
| developers.google.com | https://developers.google.com/search/docs/how-to-audit-technical-seo | — |
ChatGPT
Demo corpus · 5 URLs
Replies for “how to audit technical SEO” cluster around DebugBear, Chrome for Developers, and WebPageTest. The ones that stick define the job, then show the evidence. Northline comes up in the discussion, but the link stays with debugbear.com.
| Domain | URL | You |
|---|---|---|
| debugbear.com | https://debugbear.com/blog/how-to-audit-technical-seo | — |
| developer.chrome.com | https://developer.chrome.com/docs/how-to-audit-technical-seo | — |
| webpagetest.org | https://webpagetest.org/how-to-audit-technical-seo | — |
| searchengineland.com | https://searchengineland.com/how-to-audit-technical-seo | — |
| en.wikipedia.org | https://en.wikipedia.org/wiki/How_To_Audit_Technical_Seo | — |
AI Overviews
Demo corpus · 4 URLs
The overview for “how to audit technical SEO” is a two-sentence answer backed by developers.google.com and web.dev. Long opinion posts rarely win the link.
| Domain | URL | You |
|---|---|---|
| developers.google.com | https://developers.google.com/search/docs/how-to-audit-technical-seo | — |
| web.dev | https://web.dev/articles/how-to-audit-technical-seo | — |
| developer.chrome.com | https://developer.chrome.com/docs/how-to-audit-technical-seo | — |
| en.wikipedia.org | https://en.wikipedia.org/wiki/How_To_Audit_Technical_Seo | — |
Competitor shortlist
Domains other than yours, ranked by how many engines cited them.
- developer.chrome.comPerplexity · ChatGPT · AI Overviews/3 cites
- en.wikipedia.orgPerplexity · ChatGPT · AI Overviews/3 cites
- developers.google.comPerplexity · AI Overviews/2 cites
- web.devPerplexity · AI Overviews/2 cites
- debugbear.comChatGPT/1 cite
Three fixes for this week
Template rules from the gaps. An OpenAI key switches this block to a gpt-4o-mini narrative.
- 01
Named, not linked
Turn the ChatGPT mention into the link
Northline shows up in the answer text on ChatGPT, and the citation stays with debugbear.com.
This week
Add a table those pages don’t have: the check, the pass condition, and the tool you used. Then send debugbear.com one statistic they can quote and link, or publish https://northline.studio/answers/how-to-audit-technical-seo with a tighter title and three outbound links to the primary docs already in this report.
- 02
Missing on one engine
Close the AI Overviews gap
Northline is cited on Perplexity and missing on AI Overviews. That engine’s links are developers.google.com, web.dev, and developer.chrome.com.
This week
On https://northline.studio/answers/how-to-audit-technical-seo, put a 40–60 word definition of “how to audit technical SEO” directly under the H1, then a five-row table and FAQ schema. AI Overviews lift that shape, not a long intro.
- 03
Competitor concentration
Take the cite developer.chrome.com is getting
developer.chrome.com shows up 3 times across Perplexity, ChatGPT, and AI Overviews.
This week
Open https://developer.chrome.com/docs/how-to-audit-technical-seo. Write down the subhead they answer and you don’t. Publish that section on https://northline.studio/answers/how-to-audit-technical-seo, with one original number and three internal links from pages on your site that already get crawled.