Google Explains How They Rank PDFs and What It Means for SEO/GEO
/ 6 min read
Summary
Google's Martin Splitt explained that Google uses a converter to transform PDFs into HTML, and then it indexes the HTML. The practical question is what this changes for SEO, content quality, and AI search visibility.
For a long time, PDFs have felt like a "black box" in the world of search. We upload them for convenience or print fidelity, but we rarely know exactly how Google perceives them compared to a standard webpage. Are they treated as second class citizens, or do they carry the same weight? The same pattern also shows up in SEO Priorities to Rethink, where the practical question is how the signal becomes visible.
Recent insights from Google's John Mueller and Martin Splitt clarify this process. Understanding the mechanics of PDF indexing is no longer just about traditional SEO, but also about how your content surfaces in AI Mode and Generative Experience (GEO). If you rely on whitepapers, menus, or forms, the way you structure these files matters.
The Conversion Process: PDFs as Pseudo HTML
The most critical takeaway is that Google does not index a PDF in its native format. Instead, Google employs a converter that transforms the PDF into HTML. The search engine then indexes this HTML representation rather than the original file.
This converter sits in the pipeline immediately after rendering and just before the content enters the index. It is part of a broader system that handles various formats, including Excel sheets, rich text files, and even older formats like Lotus Notes. By turning a PDF into a web page, Google can apply its standard processing pipeline to the content.
One area of uncertainty remains regarding images. While the text is converted, it is not entirely clear if images embedded within PDFs are indexed in the same way as those on a standard webpage. Current indications suggest they might not be, though this could change as the system evolves.
Expert Interpretation: This means your PDF is essentially a "ghost" webpage. The tradeoff here is a loss of control over the final presentation. While you design a PDF for a specific visual layout, Google only cares about the resulting HTML. If your PDF relies heavily on visual cues or images to convey meaning, you are risking a significant gap in how the search engine understands your content. This connects with Google Explains when the same signal needs a clearer operating decision.
How Links Function Within PDF Files
Because of the conversion process mentioned above, links inside a PDF are not ignored. Since the converter turns the document into an HTML representation, the links are preserved and treated as standard hyperlinks. A useful companion note is We Earned 1, because it looks at a nearby part of the same system.
Google's systems are designed to handle HTML. Once the PDF is converted, the rest of the indexing and crawling infrastructure treats those links as it would any other link on the web. This allows for a flow of authority and navigation between a PDF and other pages on your site, or even external sites.
Expert Interpretation: This confirms that PDFs can be a viable part of your internal linking strategy. However, the decision to link to a PDF versus a page should be based on the user's intent. A link to a PDF is a commitment to a specific file format that may not be as responsive on mobile devices. You should inspect whether the destination of your PDF links provides a smooth transition back to your main site navigation.
Understanding PDF Size Limits
When it comes to file size, the rules for PDFs differ slightly from those of standard HTML pages. John Mueller and Martin Splitt noted that the limits for fetching a PDF are generally larger, similar to how Google handles video files or large images.
However, there is a nuance here. While the initial fetch of the PDF may have a higher ceiling, the resulting HTML representation may still be subject to standard web page limits. Google has not provided a specific byte limit for PDFs, but they indicated that these limits are dynamic and can change if the general trend of published PDFs shifts toward larger file sizes.
Expert Interpretation: While you have more breathing room with PDFs than with HTML, bloated files are still a risk. A massive PDF that takes too long to fetch or results in an oversized HTML conversion could potentially lead to indexing issues. The decision here is simple: optimize your PDFs for size without sacrificing readability. Avoid embedding unnecessarily high resolution images that don't add value to the text.
Ranking in Traditional Search and AI Mode
PDFs are eligible to rank in both traditional search results and Google's AI Mode. The reason is straightforward: once the file is converted to HTML, it is indexed just like any other document. If the content is high quality and relevant, it can surface in AI generated responses or standard blue links.
There is a major caveat, however. Not all PDFs are created equal. Some PDFs are essentially "image only" files, where the text is flattened into a picture. Google cannot convert these to HTML for ranking purposes because there is no selectable text to extract.
A simple way to test if your PDF is indexable is to try and highlight the text. If you can select the text and copy it into a plain text editor, Google can likely convert and index it. If the text is unselectable, it is effectively invisible to the search engine's text based indexing.
Regarding whether you should create PDFs, the guidance is to do so if the content warrants it. Examples include:
Documents requiring specific print formatting. Interactive forms for registrations or applications. Documents that must look identical across all devices for legal or branding reasons.
Expert Interpretation: The "highlight test" is the most practical tool you have. If your PDFs are generated by scanners without OCR (Optical Character Recognition), they are useless for SEO and GEO. The tradeoff is between visual perfection and discoverability. If you must use a PDF for design reasons, ensure you are using a text based export rather than a flattened image export.
The Pragmatic Case for HTML Over PDF
Despite the fact that PDFs can rank, the general consensus from Google is that HTML is almost always the better choice for SEO. This isn't because PDFs are "penalized," but because HTML is fundamentally easier for both search engines and users to interact with.
John Mueller uses the example of a restaurant menu. If the choice is between having a menu as a PDF or having no menu at all, the PDF is the clear winner. However, if the choice is between a PDF menu and a standard HTML webpage, the HTML page is superior. It is more responsive, easier to navigate on a phone, and more straightforward for Google to process.
The core of SEO is reducing friction. By providing content in HTML, you remove the need for a conversion step and make the content more accessible to the widest range of users and crawlers.
Expert Interpretation: This is a question of user experience versus administrative ease. It is often easier for a business to upload a PDF than to build a dedicated webpage. However, the "friction" of a PDF is a real cost. Users often dislike downloading files on mobile devices just to see a simple list of services or prices. When deciding between the two, ask yourself if the specific formatting of a PDF provides more value to the user than the accessibility of a webpage.
PDFs Are Converted To HTML
Google's Martin Splitt explained that Google uses a converter to transform PDFs into HTML, and then it indexes the HTML conversion, not the actual PDF. He also expressed uncertainty about whether images in PDFs do or do not get indexed. He. The search implication is whether the section improves the evidence around the page, not simply whether it adds more wording. Clear entities, crawlable structure, internal links, and useful context are what make the topic easier to evaluate.
The risk is usually hidden in the execution layer. A page can look fine to a human and still fail for an automated visitor if the form, call to action, rendering path, or confirmation step is not accessible enough for the agent to complete the task.
Comments
Comments are reviewed before they are published. Links are not allowed inside comments.