Every studio has habits. One of ours: before a build starts, we send the client a short reading list, five free documents, all from primary sources, none written by us. Clients who read them ask sharper questions, approve better decisions, and never get fooled by a vendor again, including by us. That's the point. Here is the list, with why each document earns its place.

1. The Google SEO Starter Guide

The foundation. Google's own explanation of how sites get discovered, understood, and ranked, written for non-specialists. If you read one document about search in your life, this is it. We wrote a [full annotated walkthrough for GCC owners](/blog/google-seo-starter-guide-annotated-for-gcc-businesses), but the original deserves your hour. Find it on Google Search Central under "SEO Starter Guide."

2. Google Search Essentials

Shorter and sterner than the starter guide: the technical requirements, the spam policies, the line between optimization and manipulation. Why clients read it: half the "growth tactics" pitched in this market sit on the wrong side of that line, and the document names them. Reading it is a vaccination.

3. AI Features and Your Website

Google's documentation on how AI Overviews and AI Mode select and cite pages. Essential in 2026 because it kills the myth of a separate "AI SEO" that costs extra: eligibility is indexation plus standard technical quality, in Google's own words. Buyers researching vendors now start inside AI answers, so understanding this document is understanding your new front door. Our take on the B2B implications is in [our AI Mode analysis](/blog/ai-mode-ai-overviews-b2b-discovery-gulf-2026).

4. The Core Web Vitals documentation on web.dev

Google's performance metrics, explained by the team that defines them: what LCP, INP, and CLS measure and what good looks like. Clients read it so that when we say "this design decision costs you half a second of LCP," the sentence means something, and so they can hold any future vendor to numbers instead of adjectives. Our commercial translation for this region lives in [the site-speed piece](/blog/website-speed-core-web-vitals-gcc-conversion).

5. The Search Console documentation

Not a concept document but a tool manual. Search Console is the free instrument panel for your web presence: indexing status, queries, performance, and, since June 2026, generative AI visibility reports. We ask every client to verify their property before kickoff, because decisions made with instruments beat decisions made with impressions. If a vendor ever resists giving you Search Console access to your own property, that resistance is the finding.

Why we outsource our credibility to Google's documentation

Because it aligns incentives. When the required reading comes from the platform rather than the vendor, the client can check everything we claim against the source we cited. Work that survives that check earns trust that no portfolio page can buy. And there's a quieter reason: these documents describe the standards we'd hold ourselves to anyway, so putting them in the client's hands costs us nothing and disciplines everyone, including us. Read the five. It's an afternoon. Then look at your current web presence and ask whether it was built by people who had. If the answer is uncertain, [that conversation is free](/contact).