Skip to main content Scroll Top

LLM SEO: The Technical Work That Decides Whether AI Can Quote You

Updated September 2026 · Written and maintained by the Progression Agency strategy team

Most sites fail before any content question arises — the crawler is blocked, or the page is empty without JavaScript. This is the technical half of AI visibility, written for the person who has to implement it.

On this page · 13 sections
  1. What is LLM SEO?
  2. What has to be true before an LLM can quote you?
  3. What does a technical LLM SEO audit actually check?
  4. Which AI crawlers should you allow?
  5. Which levers move which stage?
  6. What are the most common technical mistakes?
  7. What fixes actually work?
  8. What order should the work happen in?
  9. What should you ask a provider about the technical side?
  10. What do you deliver?
  11. How is technical LLM SEO measured?
  12. Does LLM SEO replace ordinary SEO?
  13. Video: search, AI and technical SEO

The short answerLLM SEO is the work that makes a site retrievable and quotable by large language models. Four things have to be true in order: the crawler can reach the page, the content parses without JavaScript, the passage is selected as a candidate, and the wording is clear enough to reuse. Fail the first and nothing downstream matters — which is exactly where most of the sites we audit are failing, and it is the cheapest part to fix.

Updated September 2026. Crawler names and behaviour change; the technical checks here are re-verified quarterly.

The four things an LLM has to do before it can quote you
Most sites we audit fail at step one or two, which are the cheapest to fix.

What is LLM SEO?

LLM SEO is the technical and structural work that makes a website retrievable and quotable by large language models — so an assistant can reach your page, parse it, select it, and reuse your wording rather than a competitor’s.

It is the engineering half of what is also sold as answer engine optimization and generative engine optimization. The three terms describe substantially the same practice; LLM SEO is simply the name that gets used when the conversation is with a developer rather than a marketer. We explain that overlap properly on our terminology page.

The reason it deserves its own treatment is that the technical failures are both the most common and the least discussed. Agencies sell content programmes; the sites we audit are usually failing before any content question arises.

What has to be true before an LLM can quote you?

Four things, in order: the crawler can reach the page, the content parses without JavaScript, the passage is selected as a candidate, and the wording is clear enough to reuse.

Fail the first and nothing downstream matters. Most of the money spent on this discipline is spent on the fourth while the first is quietly broken.

Reach

The crawler has to be permitted and the server has to answer. Accidental blanket disallows, bot-management rules and aggressive rate limiting are the three commonest causes, and all three are usually invisible from the browser.

Parse

The content has to exist in the HTML. Many AI crawlers execute little or no JavaScript, so a page that assembles its text client-side can return effectively empty to the systems you care about while looking perfect to you.

Retrieve

Your passage competes against every other candidate for the question. Relevance to the question as asked matters more than keyword presence, because matching happens on meaning.

Reuse

The passage has to be quotable. Hedged, meandering writing gets paraphrased into something generic and uncredited; a crisp declarative sentence gets lifted intact.

Technical checks that decide retrievability
The three at the bottom are the ones that silently cost the most.
robots.txt — Check. Which AI crawlers are allowed, and which were blocked by accident.
Server logs — Check. Which crawlers actually arrived, and what they fetched.
JS rendering — Check. What the page contains when scripts do not run.
Response time — Check. Whether fetches complete before a timeout.
Canonicals — Check. Whether duplicates split the signal.
Status codes — Check. Whether key pages return 200 to bots as well as browsers.

What does a technical LLM SEO audit actually check?

Twelve things, split between access (can a bot get the content) and structure (can a model use it once it has).

Every one of these is verifiable. None of them requires trusting a proprietary score.

robots.txt

Which AI crawlers are permitted. We find accidental blocks constantly, usually inherited from a template or added during a scraping scare and never reviewed.

Server logs

The only unarguable evidence of which crawlers arrived and what they fetched. This is the first artefact we ask for and the one most clients have never looked at.

JavaScript rendering

What each key page contains with scripts disabled. The gap between that and what you see in a browser is the gap the crawler experiences.

Response time

Whether fetches complete before the crawler gives up. Slow pages are not merely ranked lower here; they are sometimes not retrieved at all.

Canonical consistency

Whether duplicate URLs split the signal across variants, which dilutes everything downstream.

Status codes for bots

Whether key pages return 200 to crawlers as well as to browsers. Bot management sometimes serves a challenge page instead, which reads as empty content.

Schema accuracy — Check. Whether markup agrees with the visible page.
Heading structure — Check. Whether each section answers one question.
Answer position — Check. Whether the answer precedes the explanation.
Entity consistency — Check. Whether the same description appears everywhere.
Internal links — Check. Whether related pages reinforce each other.
Freshness signals — Check. Whether update dates are real and visible.

Schema accuracy

Structured data that agrees with the visible page. Markup asserting something the copy contradicts reduces machine confidence in the rest of the page.

Heading structure

Whether each section answers one question. Headings phrased as questions, with the answer immediately beneath, are measurably easier to extract.

Answer position

Whether the answer precedes the explanation. This single change moves more than any other editorial intervention we make.

Entity consistency

Whether the same description of the organisation appears everywhere, without variation. Inconsistency is why assistants describe companies wrongly.

Internal linking

Whether related pages reinforce each other, which affects both retrieval and the model’s sense of what you are authoritative about.

Freshness signals

Whether update dates are genuine and visible. Fabricated freshness is detectable and counterproductive.

The twelve checks in a technical LLM SEO audit
#CheckEvidence usedTypical failure
1robots.txt and bot managementLive file plus WAF rulesAI agents blocked by a blanket rule
2Server log crawler access90 days of raw logsNo AI user agent has ever arrived
3JavaScript-off renderingFetch without JS executionPage returns a shell and no text
4Response time under loadTimed fetches from the bot’s perspectiveRetrieval times out before the fetch completes
5Canonical consistencyRendered head versus sitemapConflicting canonicals split the signal
6Status codes served to botsRequests with each user agentBots served 403 while browsers get 200
7Schema accuracyMarkup compared to visible copyMarkup claims what the page does not say
8Heading structureRendered heading treeHeadings used for styling rather than structure
9Answer positionFirst sentence after each headingThe answer sits in paragraph four
10Entity consistencyDescriptions across site and third partiesThree different self-descriptions
11Internal linkingCrawl of the rendered siteKey pages reachable only through search
12Freshness signalsDates in markup versus real editsDates updated without content changing
Which crawlers actually matter
Directional, from our own client logs rather than a published study.
GPTBot — Crawler. OpenAI's primary training and retrieval crawler.
OAI-SearchBot — Crawler. OpenAI's search-surface fetcher.
PerplexityBot — Crawler. Perplexity's live retrieval crawler.
Google-Extended — Crawler. Controls Google AI use, separate from Googlebot.
ClaudeBot — Crawler. Anthropic's crawler.
Bingbot — Crawler. Feeds Copilot as well as Bing.

Which AI crawlers should you allow?

At minimum GPTBot, OAI-SearchBot, PerplexityBot, Google-Extended, ClaudeBot and Bingbot — unless you have a deliberate business reason to exclude one.

This is a commercial decision dressed as a technical one. Blocking protects your content from uncredited use; it also guarantees you are not cited. Most businesses selling something want to be found, and block by accident rather than by choice.

The crawlers that matter, and what each one controls
CrawlerOperated byWhat allowing it affectsBlocking cost
GPTBotOpenAITraining and retrieval for ChatGPTHigh — largest assistant audience
OAI-SearchBotOpenAIChatGPT’s search surface specificallyHigh
PerplexityBotPerplexityLive retrieval and citationHigh — most citation-dense
Google-ExtendedGoogleGoogle’s AI surfaces, separate from GooglebotModerate to high
ClaudeBotAnthropicAnthropic model accessModerate
BingbotMicrosoftBing index, which feeds CopilotHigh — also affects Bing

Blocking Google-Extended does not remove you from Google Search. It is a separate control from Googlebot, and confusing the two is a common and expensive mistake in both directions.

What each stage responds to
1 = light, 3 = heavy. Nothing moves all four, which is why single-tactic programmes stall.

Which levers move which stage?

Crawler rules move reach. Server rendering moves parsing. Answer structure moves reuse. Entity clarity moves retrieval. Nothing moves all four.

This is why single-tactic programmes stall. A schema-only engagement improves one column; an content-only engagement improves another; the site with a blocked crawler improves nothing at all until that is fixed.

Blocking everything — Mistake. A blanket disallow guarantees you are never cited.
Client-side only — Mistake. Content assembled in the browser is often invisible.
Schema theatre — Mistake. Markup that contradicts the page reduces confidence.
Burying the answer — Mistake. Six paragraphs of preamble lose the passage.
llms.txt as a strategy — Mistake. Low adoption, no ranking effect, not a substitute.
Publishing volume — Mistake. Thin pages dilute rather than accumulate.

What are the most common technical mistakes?

Blocking everything, rendering client-side only, schema that contradicts the page, burying the answer, treating llms.txt as a strategy, and publishing volume instead of clarity.

Five of these six are free to fix. The sixth is free to stop doing.

Blocking everything

Usually accidental. A rule added during a scraping scare, or inherited from a starter template, and never revisited.

Client-side rendering only

The most expensive silent failure. The page looks complete in a browser and returns nothing useful to a crawler that does not run scripts.

Schema that contradicts the page

Worse than no schema. It undermines machine confidence in everything else the page asserts.

Burying the answer

The commonest editorial failure. The answer exists, four hundred words down, and a competitor’s one-sentence version gets quoted instead.

Treating llms.txt as a strategy

Adoption is limited and it is not a ranking factor. Add it if you like; do not mistake it for the work.

Publishing volume

Thin pages dilute. One page that is genuinely the best answer outperforms fifty that restate the consensus.

What the common mistakes cost, and what fixing them costs
MistakeEffect on retrievalCost to fixTime to show up
Blanket crawler blockTotal absence from every AI surfaceMinutesDays
Client-side-only renderingPage reads as empty to most crawlersConfiguration change, occasionally a template rebuildWeeks
Schema contradicting the pageUndermines confidence in the whole pageHoursWeeks
Answer buried below the fold of the sectionPassage not selected as a candidateEditorial pass per pageWeeks
Treating llms.txt as the strategyNo measurable effect either wayAlready done; the cost is the opportunityNever
Publishing volume instead of clarityDilutes the pages that could have been citedOngoing, and usually negativeMonths
Answer first — Fix. Lead each section with the answer, then explain.
Render server-side — Fix. Put the content in the HTML, not in a script.
Open the right bots — Fix. Allow the crawlers whose surfaces you want.
One entity line — Fix. A single canonical description, used without variation.
Match the markup — Fix. Schema that restates what the page visibly says.
Measure a fixed set — Fix. Same prompts, monthly, or movement means nothing.

Want this done for your site?We build and maintain the search, content and paid programmes described on this page.

Get a free proposal

What fixes actually work?

Answer first, render server-side, allow the right bots, write one entity description, match the markup to the copy, and measure against a fixed prompt set.

Six fixes. Four of them can be done in a week by a developer who already has access.

Technical work, effort against return
llms.txt is cheap and near-worthless today. Bulk production is neither cheap nor useful.

What order should the work happen in?

Access, then rendering, then structure, then schema, then entity, then measurement. Each step depends on the one before it.

Restructuring content before confirming the crawler can reach it is the most common way to waste a quarter, and it happens because content work is easier to sell than log analysis.

The order that avoids wasted work
Restructuring before step one is the most common way to waste a quarter.
  1. Pull server logs and confirm which AI crawlers arrived in the last ninety days.
  2. Check robots.txt and any bot-management rules for accidental blocks.
  3. Render your twenty most important pages with JavaScript disabled and read what remains.
  4. Fix anything that returns effectively empty.
  5. Restructure those pages so each section answers its heading immediately.
  6. Reconcile schema with the visible copy on the same pages.
  7. Write one canonical entity description and apply it everywhere.
  8. Build a fixed prompt set and take a baseline measurement.
  9. Re-measure monthly against the same set.
  10. Re-check crawler behaviour quarterly, because it changes.

What should you ask a provider about the technical side?

Ask whether they want your server logs. Everything else in an LLM SEO pitch is assertion; the logs are the one artefact that settles the question.

Four follow-ups separate the people doing this work from the people describing it.

Will you render our templates without JavaScript, and show us the output?

This is the check that finds the expensive failure. A provider who does not run it is guessing about the single most common reason a site is invisible, and a screenshot of the rendered text costs them ten minutes.

Which crawler user agents will you test, by name?

A vague answer about ‘AI bots’ means no one has looked at a log. The names are public, the list is short, and each one behaves differently enough that testing one proves nothing about another.

What will you measure before you start, and how often afterwards?

Without a baseline taken against a fixed prompt set, any later claim of improvement is unfalsifiable. The prompt set should be written down and handed to you, not kept in-house.

What will you not do?

A provider who claims to influence every AI surface is overselling. Some surfaces are index-led and respond to conventional work; some are live-fetching and respond to technical work; none of them accept payment for placement, and the honest answer names the limits.

Want the audit rather than the checklist?

We run this as a fixed-scope technical audit and hand you the findings with the fixes prioritised.

Request an LLM SEO audit

Crawler access report — Deliverable. Which bots reached which pages, from logs.
Render audit — Deliverable. What each key page contains without JavaScript.
Schema reconciliation — Deliverable. Markup corrected to match the copy.
Answer-first rewrites — Deliverable. Restructured pages, answer leading.
Entity file — Deliverable. One description, applied everywhere.
Prompt set and baseline — Deliverable. The measurement foundation.

What do you deliver?

Six artefacts: crawler access report, render audit, schema reconciliation, answer-first rewrites, entity file, and a prompt set with a baseline.

All six are documents you keep, not a dashboard you rent.

What a technical LLM SEO audit produces
Six outputs, all verifiable, none of them a proprietary score.

How is technical LLM SEO measured?

Crawler hits in server logs, render completeness, schema validity, and then the same prompt-set measures used across all of this work.

The technical measures are binary and fast; the visibility measures are slow and probabilistic. Reporting that mixes them without saying which is which is reporting designed to look better than it is.

Technical measures versus visibility measures
MeasureTypeHow fast it movesHow certain
AI crawler hitsTechnicalDaysCertain — it is in the logs
Render completenessTechnicalImmediateCertain
Schema validityTechnicalImmediateCertain
Mention rateVisibilityWeeks to monthsProbabilistic
Citation rateVisibilityWeeks to monthsProbabilistic
Referral sessionsVisibilityMonthsUnder-reported by nature

Does LLM SEO replace ordinary SEO?

No. Assistants that lean on a search index cannot retrieve a page that is not indexed, so conventional SEO remains the foundation this work sits on.

The honest framing is that the technical bar has risen. Everything that mattered for search still matters, and three things now matter that did not: whether AI crawlers specifically are allowed, whether content survives without JavaScript, and whether your answer is extractable.

What carries over

Crawlability, indexation, site speed, internal linking, canonical hygiene and authority. All of it still applies.

What is new

AI-specific crawler permissions, render-without-JS as a hard requirement, and answer-first structure as an editorial standard.

What changes in priority

Page speed matters more, because retrieval has tighter timeouts than indexing does.

What to stop doing

Optimising thin informational pages for traffic that assistants now absorb before the click.

Video: search, AI and technical SEO

Background viewing on search and measurement. The technical material on this page is written out in full above; these are context rather than the answer to anything here.

Getting found in search

AI, AEO and what is changing

Paid media and lead generation

Websites and design

Choosing and working with an agency

Social, content and brand

By industry and by situation

Frequently asked questions

What is LLM SEO?
The technical and structural work that makes a site retrievable and quotable by large language models: the crawler can reach it, the content parses without JavaScript, the passage is selected, and the wording is clear enough to reuse.
Is LLM SEO different from AEO?
Not materially. LLM SEO is the name used when the conversation is technical; AEO is the name used when it is editorial. The deliverables overlap almost completely.
Is LLM SEO different from GEO?
No. Generative engine optimization, answer engine optimization and LLM SEO describe substantially the same practice under three labels.
Does LLM SEO replace traditional SEO?
No. Index-led AI surfaces cannot retrieve a page that is not indexed, so conventional SEO remains the foundation.
Which AI crawlers should I allow?
At minimum GPTBot, OAI-SearchBot, PerplexityBot, Google-Extended, ClaudeBot and Bingbot, unless you have a deliberate reason to exclude one.
Does blocking Google-Extended remove me from Google Search?
No. Google-Extended controls Google’s AI surfaces and is separate from Googlebot. Confusing the two is a common and expensive mistake.
Can AI crawlers read JavaScript?
Many execute little or none. A page that assembles its text client-side can return effectively empty to the systems you care about while looking perfect in your browser.
How do I check whether AI crawlers are reaching my site?
Server logs. They are the only unarguable evidence of which bots arrived and what they fetched, and most sites have never been checked.
Does schema markup help LLM visibility?
Yes, when it agrees with the visible page. Markup that contradicts the copy is worse than none because it undermines confidence in everything else on the page.
Does llms.txt matter?
Little, today. Adoption is limited and it is not a ranking factor. It is cheap to add; it is not a substitute for crawler rules or structure.
Do backlinks still matter for AI visibility?
Indirectly and substantially. They affect indexation and authority, which affect retrieval on index-led surfaces, and third-party mentions are corroboration in their own right.
How does RAG affect whether I get cited?
Retrieval-augmented generation is the stage where your page either is or is not a candidate. Everything technical on this page exists to make sure you are.
What is the single most common technical failure?
Content rendered only on the client. It is invisible in a browser test and catastrophic for retrieval.
What is the cheapest fix with the biggest return?
Unblocking the crawlers that were disallowed by accident. It costs minutes and it is the difference between candidacy and absence.
How fast do technical fixes show up?
Crawler access changes appear in logs within days. Structural changes take weeks. Visibility changes take longer and are probabilistic.
How long does an LLM SEO audit take?
A fixed-scope technical audit runs in one to two weeks, depending on how quickly we get server logs and staging access.
What does an LLM SEO audit cost?
It is scoped like any technical audit — driven by site size and how many templates need render testing, not by a per-page rate.
Do I need to rebuild my site?
Rarely. Server-side rendering for key templates is the largest change we usually recommend, and it is normally a configuration change rather than a rebuild.
Does page speed matter for LLM SEO?
More than for classic indexing. Retrieval has tighter timeouts, so a slow page is sometimes not fetched at all rather than merely ranked lower.
What is answer-first structure?
Writing the answer immediately after a question heading, then explaining. It is the single editorial change that moves the most.
How many pages should I restructure first?
The twenty that carry commercial intent. Breadth before depth wastes the work.
Should I add FAQ schema?
Only if the questions and answers genuinely appear on the page. FAQ markup without matching visible content is the classic schema mismatch.
Does content freshness matter?
For live-fetching assistants, yes. Genuine update dates help; fabricated ones are detectable and counterproductive.
Can I do this in-house?
The technical portion, yes, if you have developer access and can read server logs. The measurement infrastructure is where in-house teams usually stall.
What tools do I need?
Server log access, a way to render pages without JavaScript, a schema validator, and a repeatable method for sampling prompts. No single platform covers all four.
How do I measure whether it worked?
Technical measures from logs and rendering, which are certain and fast. Visibility measures from a fixed prompt set, which are slower and probabilistic. Report them separately.
Why is my competitor cited and I am not?
Most often one of three things: they are retrievable and you are not, their answer leads and yours is buried, or their claims are corroborated independently and yours are not.
Does this work for ecommerce?
Yes, and product and comparison pages are usually the priority. Product data that renders client-side is an extremely common failure in this sector.
Does this work for small sites?
Often better. A twelve-page site with clean rendering and answer-first structure competes well, because the technical surface is small enough to get completely right.
What should I ask a provider about the technical side?
Whether they want your server logs. A provider who does not ask for them is not checking the one thing that can be verified.
Is there a downside to allowing AI crawlers?
Your content can be used in answers without a click. That is a genuine trade-off, and it is a business decision about content rights rather than a technical one.
How often should this be re-checked?
Crawler behaviour and user agents change. Quarterly is the right cadence for a technical re-check; monthly for visibility measurement.

Sources and further reading

  1. Google Search Essentials — SEO starter guide
  2. Google: creating helpful, reliable, people-first content
  3. Google: intro to structured data
  4. Google: LocalBusiness structured data
  5. Google: FAQPage structured data
  6. Google: Article structured data
  7. Google: Product structured data
  8. Google: title links in search results
  9. Google: control your snippets
  10. Google: robots.txt introduction
  11. Google: sitemaps overview
  12. Google: consolidate duplicate URLs
  13. Google: redirects and Search
  14. Google: JavaScript SEO basics
  15. Google: multi-regional and multilingual sites
  16. Google Search Central Blog
  17. Google: get started with Search Console
  18. Google: how local search results are determined
  19. Google Business Profile: prohibited and restricted content
  20. Google Business Profile: address and service area guidelines
  21. Google Business Profile: review policy
  22. Google Business Profile: add or edit categories
  23. Google Ads: location targeting settings
  24. Google Ads: about negative keywords
  25. Google Ads: about Quality Score
  26. Google Ads: importing offline conversions
  27. Google Ads: about Smart Bidding
  28. Google Ads: about Performance Max
  29. Google Local Services Ads: eligibility and screening
  30. Google Ads: keyword match types
  31. Google Analytics 4: about conversions
  32. Google Analytics 4: attribution models
  33. US Census Bureau QuickFacts: New Jersey
  34. US Census Bureau: American Community Survey
  35. US Census: Statistics of US Businesses
  36. Bureau of Labor Statistics: New Jersey data
  37. BLS: Occupational Employment and Wage Statistics
  38. NJ Department of Labor: labor market information
  39. New Jersey Business Action Center
  40. US Small Business Administration: New Jersey district
  41. USA.gov: business resources
  42. web.dev: Core Web Vitals explained
  43. web.dev: Largest Contentful Paint
  44. web.dev: Cumulative Layout Shift
  45. web.dev: Interaction to Next Paint
  46. Google PageSpeed Insights
  47. Google Rich Results Test
  48. Google Search Console
  49. W3C Markup Validation Service
  50. Schema.org: LocalBusiness type
  51. Schema.org: Service type
  52. Schema.org: FAQPage type
  53. Schema.org: HowTo type
  54. W3C: WCAG 2.2 quick reference
  55. FTC: CAN-SPAM Act compliance guide
  56. FCC: telemarketing and robocall rules (TCPA)
  57. FTC endorsement guides — reviews and testimonials
  58. FTC: rule on consumer reviews and testimonials
  59. HHS: HIPAA guidance on online tracking technologies
  60. New Jersey Courts: attorney advertising guidelines
  61. New Jersey DCA: construction codes and permits
  62. New Jersey Home Improvement Contractor registration
  63. New Jersey Division of Consumer Affairs
  64. TikTok for Business
  65. TikTok Creative Center
  66. TikTok Ads Help Center
  67. TikTok Community Guidelines
  68. TikTok Terms of Service
  69. TikTok Privacy Policy
  70. TikTok Safety Center
  71. TikTok Transparency Center
  72. TikTok Creator Portal
  73. TikTok Newsroom
  74. TikTok for Developers
  75. TikTok advertising solutions
  76. TikTok Creator Marketplace
  77. TikTok Business Center
  78. TikTok for Business blog
  79. TikTok Creative Center: top ads
  80. TikTok Branded Content policy
  81. TikTok Shop for sellers
  82. Instagram for Business
  83. Instagram for Creators
  84. Instagram Help Center
  85. About Instagram
  86. Meta Business Suite
  87. Meta Business Help Center
  88. Meta Transparency Center
  89. About Meta
  90. Meta: Instagram platform docs
  91. YouTube Creators
  92. YouTube Official Blog
  93. YouTube Shorts help
  94. How YouTube Works
  95. YouTube Studio
  96. LinkedIn Marketing Solutions
  97. LinkedIn Help
  98. Pinterest Business
  99. Pinterest Business Help
  100. Snapchat for Business
  101. X for Business
  102. Reddit communities
  103. Reddit for Business Help
  104. ASCAP
  105. BMI
  106. SESAC
  107. Global Music Rights
  108. PRS for Music (UK)
  109. PPL (UK)
  110. SOCAN (Canada)
  111. APRA AMCOS (Australia)
  112. GEMA (Germany)
  113. SACEM (France)
  114. SIAE (Italy)
  115. JASRAC (Japan)
  116. IFPI
  117. RIAA
  118. National Music Publishers Association
  119. Harry Fox Agency
  120. SoundExchange
  121. Music Reports
  122. Epidemic Sound
  123. Artlist
  124. Soundstripe
  125. PremiumBeat
  126. AudioJungle
  127. Free Music Archive
  128. Creative Commons
  129. Incompetech
  130. FTC: advertising and marketing
  131. FTC: disclosures 101
  132. FTC: endorsement guides
  133. FTC: consumer reviews rule
  134. FTC: advertising FAQs
  135. US Copyright Office
  136. US Copyright Office: DMCA
  137. US Copyright Office: music FAQ
  138. US Copyright Office: fair use FAQ
  139. USPTO: trademarks
  140. UK Advertising Standards Authority
  141. ACCC (Australia)
  142. Competition Bureau Canada
  143. GDPR overview
  144. California Consumer Privacy Act
  145. COPPA
  146. FTC: children’s privacy
  147. W3C Web Accessibility Initiative
  148. W3C: WCAG
  149. W3C: captions
  150. W3C: making audio and video accessible
  151. ADA.gov
  152. WebAIM
  153. Epilepsy Foundation
  154. Pew Research: internet and technology
  155. DataReportal
  156. US Census Bureau
  157. US Bureau of Labor Statistics
  158. Interactive Advertising Bureau
  159. Think with Google
  160. Google Trends
  161. Nielsen insights
  162. Schema.org: VideoObject
  163. Schema.org: SocialMediaPosting
  164. Schema.org: MusicRecording
  165. Schema.org: HowTo
  166. Schema.org: FAQPage
  167. Schema.org: Organization
  168. Google: video best practices
  169. Google: video structured data
  170. CapCut
  171. Adobe Premiere Rush
  172. DaVinci Resolve
  173. Canva
  174. Descript
  175. VEED
  176. Kapwing
  177. Otter.ai
  178. Later
  179. Buffer
  180. Hootsuite
  181. Sprout Social
  182. Google Analytics
  183. Google Search Console
  184. Google Analytics developer docs
  185. GA4: events and conversions
  186. Matomo
  187. Plausible Analytics
  188. Similarweb
  189. UK Information Commissioner’s Office
  190. Office of the Privacy Commissioner of Canada
  191. Australian OAIC
  192. European Data Protection Board
  193. EU data protection
  194. EU Digital Services Act
  195. Ofcom
  196. FCC
  197. AIGA
  198. Nielsen Norman Group
  199. Smashing Magazine
  200. web.dev
  201. MDN: web media
  202. MDN: the video element
  203. ISO 21001 (reference)
  204. Buma/Stemra (Netherlands)
  205. STIM (Sweden)
  206. Teosto (Finland)
  207. Koda (Denmark)
  208. TONO (Norway)
  209. IMRO (Ireland)
  210. SGAE (Spain)
  211. ZAiKS (Poland)
  212. KOMCA (South Korea)
  213. MCSC (China)
  214. CISAC
  215. World Intellectual Property Organization
  216. TikTok: creating videos
  217. TikTok: exploring videos
  218. TikTok: privacy settings
  219. TikTok: growing your audience
  220. TikTok Creator Academy
  221. TikTok Effect House
  222. TikTok for small business
  223. Instagram: Reels help
  224. YouTube: Shorts best practice
  225. How YouTube recommends
  226. Pinterest Predicts
  227. Snapchat for Business
  228. Hootsuite blog
  229. Social Media Examiner
  230. Marketing Week
  231. Adweek
  232. Google Search Essentials — SEO starter guide
  233. Google: creating helpful, reliable, people-first content
  234. Google: intro to structured data
  235. Google: LocalBusiness structured data
  236. Google: FAQPage structured data
  237. Google: Article structured data
  238. Google: Product structured data
  239. Google: title links in search results
  240. Google: control your snippets
  241. Google: robots.txt introduction
  242. Google: sitemaps overview
  243. Google: consolidate duplicate URLs
  244. Google: redirects and Search
  245. Google: JavaScript SEO basics
  246. Google: multi-regional and multilingual sites
  247. Google Search Central Blog
  248. Google: get started with Search Console
  249. Google: how local search results are determined
  250. Google Business Profile: prohibited and restricted content
  251. Google Business Profile: address and service area guidelines
  252. Google Business Profile: review policy
  253. Google Business Profile: add or edit categories
  254. web.dev: Core Web Vitals explained
  255. web.dev: Largest Contentful Paint
  256. web.dev: Cumulative Layout Shift
  257. web.dev: Interaction to Next Paint
  258. Google PageSpeed Insights
  259. Google Rich Results Test
  260. Google Search Console
  261. W3C Markup Validation Service
  262. Schema.org: LocalBusiness type
  263. Schema.org: Service type
  264. Schema.org: FAQPage type
  265. Schema.org: HowTo type
  266. W3C: WCAG 2.2 quick reference
  267. US Census Bureau QuickFacts: New Jersey
  268. US Census Bureau: American Community Survey
  269. US Census: Statistics of US Businesses
  270. Bureau of Labor Statistics: New Jersey data
  271. BLS: Occupational Employment and Wage Statistics
  272. NJ Department of Labor: labor market information
  273. New Jersey Business Action Center
  274. US Small Business Administration: New Jersey district
  275. USA.gov: business resources

Want this done for your site?We build and maintain the search, content and paid programmes described on this page.

Get a free proposal

On Perplexity specificallyPerplexity is the assistant where technical fixes show up first. It fetches live at question time and cites densely — usually naming and linking more sources per answer than ChatGPT or Google's AI surfaces — which makes it the most useful early indicator that your crawler access and rendering work actually landed.

Why does Perplexity matter disproportionately for LLM SEO?

Because it is the shortest feedback loop available. Perplexity fetches at question time rather than relying mainly on prior knowledge, and it attaches citations to most of what it uses. If you unblock PerplexityBot and fix rendering on a Tuesday, Perplexity is where you are most likely to see evidence first.

That makes it a diagnostic instrument as much as a channel. Its audience is smaller than ChatGPT's, but a change visible in Perplexity and nowhere else usually means the work is correct and the other surfaces have not refetched yet — which is a different situation from the work being wrong.

What does Perplexity need from your site?

The same six things every AI surface needs, with two of them weighted more heavily: live fetchability and passage clarity.

PerplexityBot allowed

The crawler must not be blocked in robots.txt or by a bot-management rule. This is the single most common reason a site is absent from Perplexity specifically.

Fast response

Live retrieval has tighter timeouts than scheduled indexing. A slow page is sometimes not fetched at all rather than merely ranked lower.

Content in the HTML

Live fetching does not help if what arrives is a shell awaiting JavaScript.

Quotable passages

Perplexity cites densely, which rewards sections that answer their own heading and stand alone.

Attributed claims

Specific, sourced statements are safer to quote than confident assertions, and Perplexity quotes a lot.

Freshness

Genuine update dates help on a surface that fetches at question time. Fabricated ones are detectable and counterproductive.

How does Perplexity differ from ChatGPT and Google's AI surfaces?

Perplexity fetches live and cites densely. Google's AI surfaces lean on the Google index, so conventional SEO moves them most. ChatGPT sits between the two and has the largest audience of the three.

The practical consequence is sequencing. Technical work shows in Perplexity first, in ChatGPT's search surface next, and in Google's AI surfaces on the timescale of conventional indexing. Reading all three as one number hides that, which is why they should be measured separately even when the work is shared.

Should you optimise for Perplexity specifically?

No — optimise for retrievability and let Perplexity be the early reading. There is nothing Perplexity rewards that the others penalise, so a Perplexity-specific programme would be the same work with a narrower audience attached to it.

How the three surfaces respond to the same work

PerplexityChatGPT searchGoogle AI surfaces
Fetches live at question timeYes, heavilyYesPartly — leans on the index
Cites with linksDenselyYesSometimes
Responds fastest to crawler fixesYesSecondSlowest
Responds most to conventional SEOLeastMiddleMost
Relative audience sizeSmallestLargestLarge, but passive
Best used asAn early diagnosticThe commercial targetA conventional SEO outcome

Frequently asked questions

Does Perplexity SEO differ from LLM SEO generally?

No. The same six workstreams apply. Perplexity weights live fetchability and passage clarity more heavily, which makes it the fastest place to see whether the work landed.

Why do I appear in Perplexity but not ChatGPT?

Usually timing rather than a fault. Perplexity fetches live; other surfaces refetch on their own schedule. It generally means the work is right and has not propagated yet.

What blocks Perplexity specifically?

PerplexityBot being disallowed in robots.txt or blocked by a CDN or WAF rule, and pages too slow to be fetched inside a live retrieval timeout.

Does Perplexity cite more sources than ChatGPT?

In our observation it names and links more sources per answer, which is why it is the most useful surface for checking whether a change worked.

Should I build a separate Perplexity strategy?

No. There is nothing Perplexity rewards that the other surfaces penalise, so it would be identical work aimed at a smaller audience.

How do I check whether Perplexity can reach my site?

Server logs. Filter for PerplexityBot by name across ninety days and count the fetches — and check the URLs, not only the total.

Related

Get a free marketing proposal

Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.

Our website uses cookies from third party services to improve your browsing experience. Read more about this and how you can control cookies by clicking "Privacy Preferences".
Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.
Privacy Policy
You have read and agreed to our privacy policy
Required