Field Guides
One guide per finding that keeps coming back. Each one covers what causes it, what it costs you, exactly how to repair it, and how to confirm the repair landed rather than assuming it did.
-
One H1, and Why Your Template Probably Has Three
Multiple H1s are almost never an author decision. They come from the theme, which means one edit fixes every page on the site at once.
-
Structured Data That Says Who You Are
Most sites with structured data have the page type and nothing else. The publisher node is the piece that actually matters, and it belongs in the template.
-
The Answer Belongs in the First Paragraph
Retrieval systems quote the first passage that stands on its own. An introduction that warms up for three paragraphs gives them nothing, so they quote somebody else.
-
The noindex Nobody Meant to Ship
An accidental noindex is the most expensive one-line bug in this business, and it hides in two places, one of which never appears in view-source.
-
Your Content Is in the HTML or It Is Not
If a page needs JavaScript to show its content, most AI retrievers see an empty frame. Here is how to check what your server actually sends, and what to do when the answer is nothing.
-
Your robots.txt Is Blocking the Crawlers You Want
The AI crawler block is the most common finding QuickRankAI reports, and almost nobody who has one chose it. It takes one line to remove.