Search Off the Record

Should you publish your content as a PDF or stick strictly to standard HTML? Does Google treat PDF files differently when it comes to indexing, ranking, and AI search features? In this episode of Search Off the Record, Martin Splitt and John Mueller from the Google Search Relations team demystify how Google Search handles PDF documents. They break down some of Google's internal pipelines, explain why putting an LLMs.txt file inside a PDF is a bad idea, explore common technical traps like rasterized pages and canonicalization issues, and share practical advice on managing PDFs for SEO, AEO (SEO), and user experience. In this episode, you'll learn: Google's PDF converter pipeline: How Google converts binary PDF containers into HTML pages during indexing so the rest of the pipeline can process them normally. LLMs.txt as a PDF: Why saving an LLMs.txt file as a PDF is a bad idea, even if you like LLMs.txt. File limits & Project Gutenberg: Why crawling limits exist, and how HTML and PDF size limits function in the crawl pipeline. Rasterized pages & accessibility: How pages saved as images destroy text readability, ruin screen reader accessibility, and prevent Google from extracting text content. Canonicalization & "binary blobs": Why identical PDF downloads across different sites make canonicalization harder and how using rel="canonical" HTTP headers or embedded header links can help. PDFs for SEO in AI Overviews: How PDFs are parsed, ranked, and referenced in Google Search, AI Overviews, and broader AI systems for training and grounding. Key takeaways for SEOs & developers: HTML is preferred, and PDFs work: HTML offers better mobile responsiveness, zoom reflow, and faster loading. Internally, Google converts indexable PDF text into HTML so they can rank normally and appear in AI features. Test for text indexability: Highlight and copy text out of your PDF into a text editor; if text doesn't copy, it might be a rasterized image and can't be indexed easily. For restaurant menus: A PDF menu is better than no menu at all for restaurants, but a responsive HTML web page provides superior performance, accessibility, and user experience. Chapters 00:00 – Introduction: Welcome and setting the stage for PDF discussion. 00:50 – Can you save an LLMs.txt file as a PDF? 01:56 – Plain text vs. Binary container: What makes PDFs different from HTML? 03:08 – Inside Google's converter pipeline: Turning PDFs into HTML for indexing. 05:08 – Extracting images and links from PDF files. 06:04 – Crawling limits, file sizes, and testing cut-off thresholds. 08:35 – When does it make sense to publish a PDF? 09:33 – Do PDFs rank in Search, AI Overviews, and AI mode? 11:22 – Technical pitfalls: Rasterized pages, scanned images, and accessibility. 12:53 – Mobile connection delays, layout locking, and zoom issues. 14:12 – Canonicalization challenges with duplicate "binary blobs". 15:57 – Metadata, password protection, and updating PDF files. 18:59 – The problem with dynamic CMS PDF generation. 21:08 – The restaurant menu debate: PDF vs. HTML web pages. 23:00 – PDFs for GEO (Generative Engine Optimization) & AI grounding. 24:14 – Outro and community question. Resources Mentioned: Official Google Search Central Documentation: https://developers.google.com/search Google Search Console: https://search.google.com/search-console Don't forget to like and subscribe to the podcast on your favorite platform to catch every behind-the-scenes episode from the Search Relations team! Episode transcript → https://goo.gle/sotr115-transcript Listen to more Search Off the Record → https://goo.gle/sotr-yt Subscribe to Google Search Channel → https://goo.gle/SearchCentral Search Off the Record is a podcast series that takes you behind the scenes of Google Search with the Search Relations team. #SOTRpodcast #SEO #GoogleSearch #TechnicalSEO #GenerativeEngineOptimization Speakers: Martin Splitt, John Mueller

Sitemaps have been a core element of web development and search engine optimization for two decades, yet Search Console warnings like "Couldn't fetch" continue to generate concern among site owners. Are XML sitemaps still necessary with modern search crawlers, or can search engines and AI bots figure out site structure on their own? In this episode of Search off the Record, Google Search Relations team members Martin Splitt and John Mueller break down the history, technical specifications, and some misconceptions surrounding sitemaps, RSS feeds, LLMs.txt, canonicalization signals, and Search Console indexing behaviors. In this episode, you'll learn: The Origins of Sitemaps: How early web crawling challenges led to the sitemap standard and how building a sitemap generator started John Mueller's career at Google. Obsolete vs. Active XML Fields: Why Google dropped support for the priority and changefreq tags, and how the lastmod date is actually evaluated. XML Sitemaps vs. RSS Feeds: How RSS feeds function as lightweight sitemaps for recent updates and why AI training crawlers utilize both. Technical Limits & Index Files: The exact URL (50,000) and file size (50MB uncompressed) limits, alongside best practices for sitemap index files and robots.txt declarations. HTML Sitemaps & LLMs.txt: Why user-facing HTML maps and Markdown-based LLMs.txt files cannot replace structured XML sitemaps for search engines. Troubleshooting "Couldn't Fetch": How host load management and perceived site quality (crawl demand) trigger non-technical fetching errors in Search Console. Key takeaways for SEOs & developers: Keep Sitemaps Enabled by Default: Even for small websites or dynamic CMS setups, keeping auto-generated sitemaps active carries no downside and assists with discovery as sites grow. Provide Accurate lastmod Timestamps: Avoid setting all page timestamps to the current date; Google evaluates date reliability and will ignore lastmod signals if they are inaccurate or abused. Submit Canonical URLs Only: Always place clean, canonical versions of URLs inside your sitemap file rather than parameter-tagged tracking URLs to help guide Google's canonical selection. "Couldn't Fetch" Isn't Always a Syntax Error: If Search Console reports "Couldn't fetch" on a valid, accessible XML file, the cause is often host load throttling or low crawl demand linked to perceived site quality. Chapters 00:00 – Introduction & Welcome 00:57 – Sitemaps History & John Mueller's Path to Google 03:42 – Why Search Engines Started Using XML Sitemaps 04:46 – Deprecated Fields: Priority, Change Frequency, and lastmod 06:36 – Sitemaps for Small Sites vs. High-Volume News Outlets 08:50 – Canonical Selection & Parameterized URLs in Sitemaps 11:13 – Comparing RSS Feeds and XML Sitemaps 12:58 – Size Limits, Compression, Index Files, and robots.txt 14:15 – Custom File Naming, Privacy, and AI Crawlers 16:54 – Why HTML Sitemaps Don't Replace XML Sitemaps 19:06 – Will LLMs.txt Replace Sitemaps for AI? 22:05 – Decoding Search Console's "Couldn't Fetch" Error 24:16 – Hreflang, Image, and Video Sitemap Extensions 25:14 – Key Takeaways & Outro Resources Mentioned: Official Google Search Central Documentation: https://developers.google.com/search Google Search Console: https://search.google.com/search-console Don't forget to like and subscribe to the podcast on your favorite platform to catch every behind-the-scenes episode from the Search Relations team! Episode transcript → https://goo.gle/sotr114-transcript Listen to more Search Off the Record → https://goo.gle/sotr-yt Subscribe to Google Search Channel → https://goo.gle/SearchCentral Search Off the Record is a podcast series that takes you behind the scenes of Google Search with the Search Relations team. #SOTRpodcast #SEO #GoogleSearch #SearchConsol#SEO #WebDevelopment #GoogleSearchConsole #Sitemaps #SearchEngineOptimization #GoogleSearchRelations #LLMstxt #TechnicalSEO #SearchOffTheRecord Speakers: Martin Splitt, John Mueller