How to Build a Patent-Compliant Website: The FIF Protocol Explained
The Three Patents That Govern How Google Ranks Websites
Google has filed thousands of patents. Three of them describe the fundamental architecture of how PageRank flows through a website, how link authority is weighted, and how a site's internal structure determines its ranking ceiling. Every website that ranks permanently — not temporarily — is architecturally aligned with these three patents, whether intentionally or by accident.
What Is the FIF Protocol?
FIF stands for Full Infrastructure Framework. It is an engineering specification — not an SEO checklist — that builds websites to comply with all three patents simultaneously. The result is a website where:
Step 1: Establish the Site Architecture
Before writing a single line of content, map the site's URL structure. Every service page must be accessible at a top-level URL (e.g., /plumber-clearwater-fl), not buried in subdirectories (e.g., /services/plumbing/clearwater/florida). Subdirectory depth is the most common cause of Single-Click Architecture violations.
The homepage must link directly to every service page. If you have 50 service pages, the homepage must have 50 internal links — either in the navigation, in the body content, or in a structured directory section. This is not optional. It is the architectural requirement for US9165040B1 compliance.
Step 2: Implement Recursive Authority Flow
Every page must have at least two outgoing internal links to other pages on the site. The links must be in the main content body (not just the navigation or footer) and must use descriptive anchor text that describes the destination page's topic.
The most effective pattern is a "hub and spoke" architecture: a hub page (e.g., /plumber) links to all spoke pages (e.g., /plumber-clearwater-fl, /plumber-tampa-fl), and each spoke page links back to the hub and to two related spoke pages. This creates a recursive authority loop that maximises PageRank flow across the entire site.
Step 3: Build the Structured Data Layer
Every page needs a JSON-LD block in the <head>. For local service pages, the schema type is LocalBusiness with the following required properties: @id, name, address, telephone, areaServed, sameAs (linking to GBP, Wikidata, and major directories), and hasOfferCatalog listing all services.
Step 4: Achieve Core Web Vitals Compliance
The technical performance requirements are non-negotiable: Largest Contentful Paint under 2.5 seconds, Cumulative Layout Shift under 0.1, and Interaction to Next Paint under 200ms. These are not just performance metrics — they are ranking signals. Google confirmed in 2021 that Core Web Vitals are a ranking factor, and the threshold for "Good" has been tightening with each annual update.
The only reliable way to achieve these scores on a content-heavy site is server-side rendering. Client-side rendered sites (React SPA, Vue SPA) consistently fail LCP because the browser must download, parse, and execute JavaScript before rendering any content. Server-side rendering delivers pre-rendered HTML to the browser, achieving LCP in under 500ms on a standard CDN.
Step 5: Configure Crawl Infrastructure
The final step is ensuring Google can discover and crawl every page. This requires: a correctly configured robots.txt that does not accidentally block important pages; an XML sitemap index that references all sub-sitemaps; and canonical URLs on every page that prevent duplicate content from diluting authority across URL variants.
For sites with large page counts (10,000+), the sitemap must be split into sub-sitemaps of no more than 50,000 URLs each, with a sitemap index at /sitemap.xml referencing all sub-sitemaps. This is the architecture used by this site, which serves over 85,000 niche pages across 13 countries.
The Full Specification
The complete FIF Protocol specification — including the seven-step implementation checklist, the structured data templates, and the Core Web Vitals audit framework — is available at the FIF Protocol spec page. It is the engineering document we use for every client engagement.