Skip to content
Request a quote
info@ibramdawwa-gmbh.deRegensburg, Germany ·
[SL: 01]SEO I&D Systems × I&D Studio

SEO, checked and cited.

We check your site against 138 technical requirements we compiled from Google's public documentation and Search Central Live 2026, then fix what we find. Tell us your URL and get a scoped quote.

Nothing is scanned. This starts your quote request.

What you need

Each pick goes into your quote request. You can change it any time.

Free quote. Reply within 1 business day. No price list: we quote on your site, not on a package.

Start with your situation

The knowledge base behind the work

Knowledge base v2.13.0 · data through 2 October 2026

Claims, each labelled by who said it
2,228
Requirements in 16 areas
138
Sources, each with a checked date
242
Access
Free and public

Independent. Not affiliated with or endorsed by Google.

[SL: 02]Where you are

Start with your situation.

8 situations we get asked about. Pick yours to see which areas we’d check first and what we’d do, and add it to your quote as you go.

Not sure which one fits?

Every situation draws on the same 138 requirements in 16 areas. Pick the one closest to yours, or send us your URL and we’ll scope it with you.

Request a quote

Requirements board

138 requirements · 129 documented in Google’s docs · 9 said at Search Central Live only

Select an area to add it to your quote.

The 138 requirements by area and level

  • Server, status codes and crawling: 11 requirements (Must 6, Should 1, Avoid 4)
  • URLs, links and discovery: 11 requirements (Must 6, Should 4, Avoid 1, Said at Search Central Live only 1)
  • Rendering and JavaScript: 10 requirements (Must 2, Should 6, Avoid 2, Said at Search Central Live only 1)
  • Indexing and snippet controls: 13 requirements (Must 1, Should 6, May 4, Avoid 2)
  • Canonicals, redirects and duplicates: 11 requirements (Must 6, Should 2, Avoid 3)
  • Error pages and soft 404s: 4 requirements (Must 2, Should 1, Avoid 1)
  • International and multilingual sites: 12 requirements (Must 4, Should 6, May 1, Avoid 1, Said at Search Central Live only 1)
  • Page structure and HTML: 7 requirements (Must 1, Should 4, May 1, Avoid 1, Said at Search Central Live only 1)
  • Structured data: 15 requirements (Must 2, Should 11, May 1, Avoid 1, Said at Search Central Live only 2)
  • Shopping data: 4 requirements (Should 3, May 1, Said at Search Central Live only 1)
  • Images: 8 requirements (Must 2, Should 5, May 1)
  • Video: 6 requirements (Must 1, Should 4, May 1)
  • Performance and server capacity: 4 requirements (Should 3, May 1, Said at Search Central Live only 1)
  • AI features: 6 requirements (Must 1, Should 3, May 2, Said at Search Central Live only 1)
  • Spam policies and AI content: 5 requirements (Must 1, Should 1, Avoid 3)
  • Testing and monitoring: 11 requirements (Must 2, Should 7, May 2)
  • All areas: 138 (Must 37, Should 67, May 15, Avoid 19, Said at Search Central Live only 9)
All 138 requirements, with sources, in our free knowledge base (opens in a new tab)

Knowledge base v2.13.0 · data through 2 October 2026

Independent. Not affiliated with or endorsed by Google.

Starting areas are our judgement, not a diagnosis. Your quote is based on your site.

Request a quote
[SL: 03]Services

Everything we do for search.

13 services in 4 groups, from a one-off check to agents that keep checking. We fix and build ourselves, so findings don’t stop at a PDF. Add what you need and it goes straight into your quote request.

  1. (A)Check2 services

    1. 01

      Requirements check

      Your site against the 138 requirements in 16 areas, with the ones that don’t apply marked n/a. Every finding cites its requirement and its source.

      Deliverables:

      • Cited findings report
      • Ticket-ready CSV
      • Pre-launch checklist
    2. 02

      Deep audit

      The check, plus what Google actually fetched: crawl and index analysis from read-only Search Console access and your server logs.

      Deliverables:

      • Crawl and index analysis
      • Search Console + server logs
      • Priority plan

  2. (B)Fix and build3 services

    1. 03

      Implementation and fixes

      We fix what we find in your codebase or CMS, then re-test each fix against the same requirement.

      Deliverables:

      • Fixes in your codebase or CMS
      • Re-tested per requirement
      • Handover notes
    2. 04

      SEO-ready website builds

      New websites from I&D Studio, built to the requirements from the first commit instead of patched afterwards.

      Deliverables:

      • Built to the requirements
      • EN / DE
      • Structured data
      See how we build websites
    3. 05

      Relaunches and migrations

      Domain, platform or URL changes with a redirect map, a canonical plan and checks before and after go-live.

      Deliverables:

      • URL map
      • Redirect and canonical plan
      • Pre- and post-launch checks

  3. (C)Specialist tracks4 services

    1. 07

      International and hreflang

      Language and country versions Google can tell apart: URL structure, hreflang and canonicals that agree with each other.

      Deliverables:

      • Language and country URLs
      • hreflang + canonicals
      • Validation
    2. 08

      JavaScript rendering

      For sites on JavaScript frameworks: we test what Google renders and check that links and metadata match the server’s HTML.

      Deliverables:

      • Rendering tests
      • SSR and hydration checks
      • Link and metadata parity
    3. 09

      Shop and product data

      Product pages, Merchant Center data and structured data that tell the same story, down to images and video.

      Deliverables:

      • Product structured data
      • Merchant Center data checks
      • Image and video data

  4. (D)In your AI tools4 services

    New services. Scope and timeline agreed at scoping.

    How it fits into your tools
    1. 10

      Knowledge-base MCP server

      The knowledge base plus your guidelines in Claude, Cursor or your internal agents, running in your infrastructure.

      Deliverables:

      • Knowledge base + your guidelines
      • Claude, Cursor, internal agents
      • Runs in your infrastructure
    2. 11

      Auditor agent

      Checks your sites and every release on a schedule, and opens tickets that cite the requirement they break.

      Deliverables:

      • Scheduled checks
      • Per-release checks
      • Cited tickets in your tracker
    3. 12

      Private or local AI

      The knowledge base and your own docs behind a model on your hardware or private cloud, answering with claim IDs.

      Deliverables:

      • Your hardware or private cloud
      • Knowledge base + your docs
      • Answers with claim IDs
    4. 13

      Kept current, monthly

      Monthly updates to your installation as the knowledge base and its requirements change.

      Deliverables:

      • Knowledge-base release updates
      • Requirement updates
      • Installation check

Timeline agreed at scoping for every service. First blueprint: 72 h target after kickoff.

Independent. Not affiliated with or endorsed by Google.

In your quote:0

Request a quote
[SL: 04]What you get

Every finding comes with its receipt.

Not “consider improving your site”. A requirement, a level, a test your developer can run, and the source it rests on, with the date we last checked it.

Example ticket

Quoted from the developer kit. Long fields are cut to their first sentence.

Developer kit v2.13.0

Requirement ID
DEV-SRV-01 (opens in a new tab)
Level(01)
MUST
Area
Server, status codes and crawling
Requirement
Let verified Google crawlers through firewalls, CDNs and bot protection
Why(02)
Google does not know that a firewall or bot-protection rule is blocking it; it only sees failing requests.
How
Allowlist Google's crawlers in WAF, CDN and bot-management rules by the IP ranges Google publishes for its common and special-case crawlers (common-crawlers.json, special-crawlers.json), or by reverse DNS to crawl-*.googlebot.com or geo-crawl-*.geo.googlebot.com hosts; never by user-agent string alone (it is trivial to fake), and never by a whole googleusercontent.com host, where Google Cloud customers' machines resolve too.
Test(03)
Search Console Crawl stats report: host status shows no robots.txt fetch, DNS resolution or server connectivity failures, and no Search Console alert for DNS errors.
Basis(04)
DocumentedStated or supported by Google's documentation.
Source
Crawling December: CDNs and crawling (opens in a new tab)checked 4 October 2026
Page tested
your-site.com/…
Status
One of:
  • Pass
  • Finding
  • n/a
Set for your page when we test it.

How to read it

  1. (01)Level

    MUST, SHOULD, MAY or AVOID, so your team knows what comes first.

  2. (02)Why

    Why it matters, in one sentence.

  3. (03)Test

    How to prove the fix worked. Your developer can run it without us.

  4. (04)Basis and source

    Google's documentation, or said at Search Central Live only. Linked to the source, with the date we checked it.

  5. (05)One row per ticket

    Every ticket is one CSV row, ready to import into Jira, Linear or GitHub Issues.

One row per ticket

(05)
id,level,area,requirement,url,status,why,how,test,basis,source,checked

Example format from the free developer kit, built from a real requirement. Not a client finding.

In the free developer kit · Knowledge base v2.13.0 · data through 2 October 2026

  • 138requirements
  • 129documented in Google's docs
  • 9said at Search Central Live only
  • 35code snippets
  • 56MUST and AVOID items on the pre-launch checklist
  • CSVof every requirement, ticket-ready

Independent. Not affiliated with or endorsed by Google.

Request a quote for the 138-requirement checkBrowse the free developer kit (opens in a new tab)
[SL: 06]I&D Systems · In your AI tools

The reference, inside your own tools.

Your team already asks AI about SEO. We make the answers cite their sources: the knowledge base and your own guidelines, set up in your infrastructure, inside the tools your team already uses.

New services. Scope and timeline agreed at scoping.

Illustration: The knowledge base, your guidelines and your docs feed an MCP server that runs in your infrastructure. Claude, Cursor, your internal agents and an auditor agent all draw on it, and the auditor agent opens cited tickets in your tracker.

Claude and Cursor are examples. Trademarks belong to their owners.

What we set up

  • (10)

    Knowledge-base MCP server

    One server, in your infrastructure. Claude, Cursor and your own agents answer from the knowledge base and your guidelines, and cite the source.

  • (11)

    Auditor agent

    Checks your sites and releases on a schedule. Every ticket it opens in your tracker names the requirement and its source.

  • (12)

    Private or local AI

    When your docs can’t leave the house: the same setup behind a model on your own hardware or private cloud.

  • (13)

    Kept current, monthly

    Each month your setup moves to the current knowledge-base release, so answers and checks follow the requirements as they change.

Ask for a quote on an AI tools setupExplore I&D Systems

Free and public: the agent pack

Part of our free knowledge base of Search Central Live Deep Dive Europe 2026. Every setup starts from it.

Independent. Not affiliated with or endorsed by Google.

The agent pack on GitHub (opens in a new tab)
  • agent-pack/

    The whole knowledge base as JSON: all 2,228 claims and 138 requirements, with topics, sessions and sources.

  • AGENTS.md

    Instructions that make agents answer with a claim ID for every fact.

  • kb_query.py

    An offline query tool that answers from the pack alone.

  • eval/

    An eval harness with test questions, to check the answers you get.

[SL: 07]Free knowledge base

We did the reading. It stays free.

Three days of Search Central Live in Barcelona, turned into an open knowledge base. Every claim is labelled by who said it and graded against Google's documentation. Read it, search it, plug it into your own tools. When you want it applied to your site, that's where we come in.

The knowledge base in numbers

claims, each labelled by who said it
2,228
sessions with claims
44
sources, each with a checked date
242
topics in 14 areas
96
things, from Googlebot to hreflang
90
slide and stage claims, graded against Google's documentation
1,317
What's on screen
  1. 01

    Into the water

    An underwater intro. The Diver bot swims in, with the line: Barcelona, three days, every word checked.

  2. 02

    Every point labelled

    Claim cards stack up. Each one carries a label for who said it (slide, stage, Google docs, press or author analysis) and its grade.

  3. 03

    Every point checked against Google's documentation

    The same cards, sorted by what Google's own documentation says about each claim.

  4. 04

    Three days, three field guides

    Day 1 Crawling, Day 2 Indexing, Day 3 Serving. One PDF field guide per day.

  5. 05

    The web edition, the Reef map and the kits

    The searchable web edition, the Reef map of how everything connects, the developer kit, the media kit, and the agent pack you can ask questions.

  6. 06

    The counters

    2,228 claims, 96 topics, 242 sources, and 67% of graded claims backed by Google's documentation.

  7. 07

    End card

    The Knowledge Base. Notes, analysis and verification by Ibrahim Anjro. An independent attendee resource, not affiliated with or endorsed by Google.

Independent. Not affiliated with or endorsed by Google.

Independent attendee knowledge base of Search Central Live Deep Dive Europe 2026, Barcelona, 30 September – 2 October 2026. Made by Ibrahim Anjro of Ibram & Dawwa.

Knowledge base v2.13.0 · data through 2 October 2026

Want it applied to your site? Send us your URL.

Request a quoteOpen the knowledge base (opens in a new tab)

6 ways in

[SL: 08]How a quote happens

From your URLto a quote.

Why no prices? Because a five-page site and a shop in six languages are different jobs. This is how you get yours.

The quote is free and without obligation.

  1. (01)

    Send your site

    Your URL and what you need. Two minutes, no passwords, no budget field.

  2. (02)

    We look, then reply

    We read your request and look at your site. You hear back within 1 business day, with questions or a first scope.

  3. (03)

    Scoping call and written quote

    We agree areas, access and deliverables, then you get the quote in writing. If a deep audit needs it, you grant read-only Search Console and log access, and you can revoke it anytime. Timeline agreed at scoping.

  4. (04)

    Kickoff

    We start on the agreed scope. The first blueprint is a 72 h target after kickoff: what we check first, in which order, and who fixes what.

Target: the first blueprint 72 hours after kickoff.

Everything else: timeline agreed at scoping.

Start with your URL
[SL: 09]FAQ

Straight answers.

Before you ask.

01Why are there no prices?
Because we quote on your site, not on a package. Size, platform, languages and what you need change the work. Send your URL and you get a written quote, free and without obligation.
02Can you guarantee rankings?
No, and nobody honest can. What we commit to: every requirement in scope checked, every finding cited, every fix tested.
03Are you affiliated with Google?
No. Independent. Not affiliated with or endorsed by Google. The knowledge base is an attendee's record of Search Central Live Deep Dive Europe 2026. Every finding links to its source, and to Google's own documentation wherever it exists.
04Do you need our passwords?
No, and please don't send any. The requirements check needs your URL. If a deep audit needs Search Console or server logs, you grant read-only access later and can revoke it anytime.
05Is the check automated?
It's done by people, with our own tooling. Every finding is reviewed before it reaches you.
06We already have developers. Where do you fit in?
Good. Findings come as a ticket-ready CSV with a why, a how and a test for each. Your team fixes, we fix, or both.
07We're planning a relaunch. When should we talk?
Before the URLs change. Redirect maps and canonical plans are easier to get right before launch than after.
08With the MCP server or private AI, where does our data stay?
In your infrastructure. We set it up there, next to your own guidelines.
09Is the knowledge base really free?
Yes, and it stays free and public. The quote is for applying it to your site.
10Do you work in German?
Yes, in German and English. The knowledge base itself is English-only.
[SL: 10]Request a quote

Tell us where you are.We’ll tell you what it takes.

Your site and what you need. No price list, no budget field, no obligation. We reply within 1 business day.

In your quote

Nothing picked yet. That’s fine: send your site and we check first, then advise.

Direct line

(01) Email
info@ibramdawwa-gmbh.de
(02) Phone
+49 1575 1702770
(03) Regensburg
(local time in Regensburg)
(04) Reply
within 1 business day
Request a quote