Zum Inhalt springen
regensbot
URL kostenlos prüfenAnmelden

AnforderungenSearch Central Live Deep Dive Europe 2026

138 Anforderungen, jede mit Quelle.

Das Entwickler-Kit von Search Central Live Deep Dive Europe 2026, in 16 Bereichen. Jede Anforderung sagt, was zu tun ist, warum es zählt, wie Sie es umsetzen und wie Sie es prüfen, und nennt die Google-Dokumente und Aussagen, auf denen sie beruht.

Die Anforderungen stehen im englischen Original.

Nach Stufe

  • Muss37
  • Sollte67
  • Kann15
  • Vermeiden19

Abdeckung, wenn alle Quellen verbunden sind

  • Automatisch105
  • Unterstützt29
  • Geführt4

Pack v2.13.0Daten bis 2026-10-02Die Wissensbasis (öffnet in einem neuen Tab)

SRV01 / 16

Server, status codes and crawling

11 Anforderungen

How the server answers Google's crawlers decides whether anything else on the site matters. These requirements cover reachability through firewalls and CDNs, status codes for outages and overload, robots.txt on every host, HTTP versions and caching headers.

  1. DEV-SRV-01MussLet verified Google crawlers through firewalls, CDNs and bot protectionUnterstütztServer-Logs
  2. DEV-SRV-02VermeidenNever serve bot challenges or error pages to crawlers with a 200 statusAutomatischEine URL
  3. DEV-SRV-03MussAnswer planned maintenance and short outages with 503, for a day or two at mostUnterstütztIhre Website
  4. DEV-SRV-04MussKeep robots.txt reachable on every host: 200 with rules, or 404 if there are noneAutomatischEine URL
  5. DEV-SRV-05MussRely only on the fields Google supports (user-agent, allow, disallow, sitemap) and keep robots.txt under 500 KiBAutomatischEine URL
  6. DEV-SRV-06VermeidenDo not put Content-Signal or other non-standard lines between user-agent linesAutomatischEine URL
  7. DEV-SRV-07MussAnswer crawlers over HTTP/1.1 (HTTP/2 optional); never run a crawlable host on HTTP/3 onlyAutomatischEine URL
  8. DEV-SRV-08SollteSupport conditional requests with ETag or Last-Modified and answer 304 when nothing changedAutomatischEine URL
  9. DEV-SRV-09VermeidenDo not answer crawlers with 401, 402 or 403 on pages that should be in SearchAutomatischGoogle
  10. DEV-SRV-10MussGive a crawler its own robots.txt group only when needed, and make that group completeAutomatischEine URL
  11. DEV-SRV-11VermeidenNever use robots.txt to hide private paths; protect them with authenticationAutomatischEine URL

REN03 / 16

Rendering and JavaScript

10 Anforderungen

Google renders pages with a headless Chromium in a separate, queued system and indexes what is in the DOM when rendering ends. Content and links that depend on clicks, scrolling, blocked resources, permission prompts or slow APIs can be missing from what Google indexes.

  1. DEV-REN-01SollteServer-render the main content and everything indexing depends on (SSR, static generation or hybrid)AutomatischRendering
  2. DEV-REN-02MussHave all indexable content in the DOM after load, without clicks, typing or scrollingAutomatischRendering
  3. DEV-REN-03MussLazy-load with native lazy loading or an IntersectionObserver, never with scroll eventsAutomatischRendering
  4. DEV-REN-04VermeidenDo not block JavaScript, CSS or API endpoints that pages need for rendering in robots.txtAutomatischRendering
  5. DEV-REN-05VermeidenDo not add, change or remove robots meta tags with JavaScriptAutomatischRendering
  6. DEV-REN-06SollteMake rendering robust: no slow API dependencies and no unresolved placeholdersAutomatischRendering
  7. DEV-REN-07SollteKeep prices, offer counts and other commercial data identical in raw and rendered HTMLAutomatischRendering
  8. DEV-REN-08SollteFeature-detect permission-based APIs and WebGL, and render the content without themAutomatischRendering
  9. DEV-REN-09SollteMonitor JavaScript console errors and Content Security Policy violations on key templatesAutomatischRendering
  10. DEV-REN-10SollteKeep indexable content out of iframes, and check web components in the rendered HTMLAutomatischRendering

IDX04 / 16

Indexing and snippet controls

13 Anforderungen

robots.txt controls crawling; the robots meta tag and the X-Robots-Tag header control indexing and how a page appears, including how much of it AI Overviews and AI Mode may use. Search Console and the Google-Extended token add controls for generative AI.

  1. DEV-IDX-01MussUse noindex to keep a page out of Search, and leave that URL crawlableAutomatischEine URL
  2. DEV-IDX-02VermeidenDo not use noindex, nofollow or crawl-delay to save crawl budgetAutomatischServer-Logs
  3. DEV-IDX-03SollteSend robots rules for PDFs, images and other non-HTML files in the X-Robots-Tag headerAutomatischEine URL
  4. DEV-IDX-04SollteAllow full snippets and large previews with max-snippet:-1 and max-image-preview:largeAutomatischEine URL
  5. DEV-IDX-05VermeidenDo not add nosnippet or a short max-snippet unless you accept losing snippets and AI feature useAutomatischEine URL
  6. DEV-IDX-06SolltePrefer rel attributes on individual links to a page-level nofollowAutomatischEine URL
  7. DEV-IDX-07KannUse data-nosnippet on a span, div or section to keep one detail out of snippetsAutomatischEine URL
  8. DEV-IDX-08KannUse unavailable_after on pages with a known end dateAutomatischEine URL
  9. DEV-IDX-09SollteLeave notranslate and noimageindex out of templates unless translation or image indexing must be preventedAutomatischEine URL
  10. DEV-IDX-10KannUse the Search generative AI setting in Search Console only to take a property out of AI Overviews and AI ModeGeführtIhre Website
  11. DEV-IDX-11KannUse the Google-Extended robots.txt token to control Gemini training and groundingAutomatischEine URL
  12. DEV-IDX-12SollteOn sites with explicit content, keep it on its own subdomain or domain and label it with rating markupUnterstütztIhre Website
  13. DEV-IDX-13SollteFor an urgent removal, use the Removals tool in Search Console and also return 404 or noindexUnterstütztIhre Website

CAN05 / 16

Canonicals, redirects and duplicates

11 Anforderungen

Google clusters duplicate pages, picks one representative URL (the canonical) and forwards signals to it. Redirects, rel=canonical, internal links and sitemaps tell it which URL you prefer: when they agree Google follows them, and when they conflict it decides on its own.

  1. DEV-CAN-01MussUse permanent server-side redirects (301 or 308) for moved URLs, straight to the final URLAutomatischEine URL
  2. DEV-CAN-02MussServe one host over HTTPS with a valid certificate and redirect every other origin to itAutomatischEine URL
  3. DEV-CAN-03MussPut exactly one absolute rel=canonical in the server-rendered head of every indexable pageAutomatischEine URL
  4. DEV-CAN-04MussPoint every canonical directly at a final URL that returns 200, is indexable and is linkedAutomatischCrawl
  5. DEV-CAN-05MussMake all canonical signals agree: redirects, rel=canonical, internal links, sitemaps and hreflangAutomatischCrawl
  6. DEV-CAN-06VermeidenDo not canonicalise one language version to another; connect them with hreflangAutomatischEine URL
  7. DEV-CAN-07VermeidenNever leave staging, preview or mirror copies of the site publicly crawlableAutomatischEine URL
  8. DEV-CAN-08SollteMake pages that share a URL pattern differ in their main contentAutomatischCrawl
  9. DEV-CAN-09SollteKeep migration redirects in place long term and judge a move in Search Console, not with site: queriesUnterstütztIhre Website
  10. DEV-CAN-10MussRedirect an old URL only to a page with the same intent, and return 404 or 410 when there is noneUnterstütztIhre Website
  11. DEV-CAN-11VermeidenNever route a crawlable URL's redirects through a URL that robots.txt blocksAutomatischEine URL

ERR06 / 16

Error pages and soft 404s

4 Anforderungen

A page that should be an error but returns 200 is a soft 404: Google keeps it out of the index but keeps crawling it, may cluster many such pages together, and recognises it from the main content rather than from keywords. Every response needs the status code that matches the state of the page.

  1. DEV-ERR-01MussReturn 404 or 410 for removed and non-existent URLsAutomatischEine URL
  2. DEV-ERR-02MussReturn a real 404 for unknown routes in single-page apps, or use a documented client-side fallbackAutomatischRendering
  3. DEV-ERR-03VermeidenNever serve error states, empty results or failed data loads with a 200 statusAutomatischEine URL
  4. DEV-ERR-04SollteKeep temporarily out-of-stock product pages live with 200 and their current availabilityAutomatischEine URL

INT07 / 16

International and multilingual sites

12 Anforderungen

Google reads a page's language from its content, stores one language per page and uses hreflang to show searchers the right version. Each version needs its own URL, crawlable links to its alternates, valid and reciprocal annotations and content that really differs.

  1. DEV-INT-01MussGive every language and country version its own URLAutomatischEine URL
  2. DEV-INT-02VermeidenDo not redirect visitors automatically by IP address or browser languageAutomatischEine URL
  3. DEV-INT-03MussMake hreflang complete: a self-reference, return links and fully qualified URLsAutomatischCrawl
  4. DEV-INT-04MussUse valid hreflang codes: an ISO 639-1 language, an optional ISO 15924 script and an optional ISO 3166-1 Alpha-2 regionAutomatischEine URL
  5. DEV-INT-05SollteSupply hreflang through one method only: HTML head, HTTP Link header or sitemapAutomatischEine URL
  6. DEV-INT-06MussBuild language and market selectors as <a href> links to each alternate URLAutomatischRendering
  7. DEV-INT-07SollteMake each page's language unambiguous by translating the template with the main contentAutomatischEine URL
  8. DEV-INT-08SollteDifferentiate same-language country versions beyond boilerplate and mark them with region codesAutomatischCrawl
  9. DEV-INT-09KannChoose ccTLDs, subdomains or subdirectories by business needs, and never URL parametersAutomatischEine URL
  10. DEV-INT-10SolltePublish machine-translated language versions only after human review and localisationUnterstütztCrawl
  11. DEV-INT-11SollteWrite pages in the words, spellings and script the audience searches with, and never add synonym or variant listsUnterstütztIhre Website
  12. DEV-INT-12SollteMark the text direction of right-to-left and mixed-script titles, product names and URLsUnterstütztIhre Website

HTM08 / 16

Page structure and HTML

7 Anforderungen

Google parses each page into a DOM, tells header, navigation, main content and footer apart, and weighs words by where they appear. Templates decide whether the main content is easy to find and whether controls in the HTML work as intended.

  1. DEV-HTM-01SollteWrap each page's primary content in one clearly delimited main areaAutomatischEine URL
  2. DEV-HTM-02SolltePlace the words a page should rank for in its main content, not in footers or sidebarsUnterstütztIhre Website
  3. DEV-HTM-03MussGive every indexable page a unique, descriptive title element in the server HTMLAutomatischCrawl
  4. DEV-HTM-04SollteUse semantic, accessible HTML: real buttons, labelled forms and a logical heading orderUnterstütztIhre Website
  5. DEV-HTM-05SollteWrite valid HTML and close every elementAutomatischEine URL
  6. DEV-HTM-06VermeidenNever hide text from users, such as white-on-white or off-screen keyword blocksUnterstütztRendering
  7. DEV-HTM-07KannUse real heading, title and emphasis elements instead of styling aloneAutomatischRendering

SDA09 / 16

Structured data

15 Anforderungen

Structured data makes pages eligible for rich results, gives Google precise facts such as prices, dates and identifiers more cheaply and accurately than model-based extraction, and the same processed data feeds classic results and AI features. It must describe what users can see.

  1. DEV-SDA-01SollteWrite structured data as JSON-LD by defaultAutomatischEine URL
  2. DEV-SDA-02MussMark up only content that is visible on the page and relevant to itUnterstütztIhre Website
  3. DEV-SDA-03SollteChoose the specific types Google documents for its features, and skip generic or irrelevant onesAutomatischEine URL
  4. DEV-SDA-04SollteIdentify entities with unique identifiers: url, @id and stable IDsAutomatischCrawl
  5. DEV-SDA-05SollteWrite dates in ISO 8601 and give every date-time a UTC offsetAutomatischEine URL
  6. DEV-SDA-06SollteEmit each structured data entity once per page, and audit CMS plug-ins for duplicatesAutomatischEine URL
  7. DEV-SDA-07SollteDescribe only the page's main product in Product markup, not related-product carouselsAutomatischEine URL
  8. DEV-SDA-08SollteMark up merchant listings completely, with validity dates for sale pricesAutomatischEine URL
  9. DEV-SDA-09SollteDeclare return, shipping and loyalty policies once at organisation levelAutomatischEine URL
  10. DEV-SDA-10SolltePut the same structured data on duplicate URLs as on the canonicalAutomatischEine URL
  11. DEV-SDA-11MussValidate markup in the Rich Results Test before it reaches templates, and monitor it after releaseUnterstütztCI
  12. DEV-SDA-12KannWire Google's SHACL validation rules into the build once they are publishedGeführtIhre Website
  13. DEV-SDA-13SollteAdd Article markup with headline, images, dates and authors to every article templateAutomatischEine URL
  14. DEV-SDA-14VermeidenDo not mark up self-serving review ratings of your own businessAutomatischEine URL
  15. DEV-SDA-15SollteState the preferred site name with WebSite markup on the home pageAutomatischEine URL

SHP10 / 16

Shopping data (Merchant Center, product markup and Storebot)

4 Anforderungen

Product rich results come from structured data, the Shopping tab needs a Merchant Center feed, and Google Shopping's own crawler, Storebot-Google, checks both against the shop. AI shopping experiences ask for richer product data than classic results, delivered first through the feed.

  1. DEV-SHP-01SollteUse Product markup for rich results and a Merchant Center feed for the Shopping tab, with identical valuesAutomatischGoogle
  2. DEV-SHP-02SollteLet Storebot-Google crawl product, cart and checkout pages, through robots.txt and bot protectionAutomatischServer-Logs
  3. DEV-SHP-03SollteSend conversational product data in the Merchant Center feed: Q&A, product details, highlights and related productsAutomatischGoogle
  4. DEV-SHP-04KannTreat product Q&A and specification markup in schema.org as an extra on top of the feedAutomatischEine URL

IMG11 / 16

Images

8 Anforderungen

Google finds images through img elements in the HTML and through image sitemaps, understands them through alt text and the surrounding text, and can show them in web search, Google Images, Discover and AI features.

  1. DEV-IMG-01MussPut every image that should be found in an <img> element with a src attributeAutomatischRendering
  2. DEV-IMG-02MussDescribe every meaningful image in its alt attributeAutomatischEine URL
  3. DEV-IMG-03SolltePlace images next to text that explains themUnterstütztIhre Website
  4. DEV-IMG-04SollteList important images in an image sitemapAutomatischEine URL
  5. DEV-IMG-05SollteServe modern, compact image formats with a widely supported file in the img srcAutomatischEine URL
  6. DEV-IMG-06SollteKeep images out of Search with robots.txt or X-Robots-Tag, not with CSS tricksAutomatischEine URL
  7. DEV-IMG-07SollteGive every article a large, relevant lead image and declare it in og:image or markupAutomatischEine URL
  8. DEV-IMG-08KannKeep the IPTC and C2PA metadata that marks AI-generated imagesUnterstütztIhre Website

VID12 / 16

Video

6 Anforderungen

Google extracts videos from the page together with the data around them and passes them to its media indexing. A dedicated watch page, a video element that loads without interaction and VideoObject markup make a video eligible for video features such as key moments.

  1. DEV-VID-01MussEmbed each video in a video, iframe, embed or object element that loads without user actionAutomatischRendering
  2. DEV-VID-02SollteGive each important video its own watch pageUnterstütztGoogle
  3. DEV-VID-03SollteDescribe videos with VideoObject markup and mark key moments with Clip or SeekToActionAutomatischEine URL
  4. DEV-VID-04SollteList videos in a video sitemapAutomatischEine URL
  5. DEV-VID-05KannAllow video previews with max-video-preview:-1AutomatischEine URL
  6. DEV-VID-06SollteServe videos fast in a common container with standard codecs, and never block the filesAutomatischEine URL

PRF13 / 16

Performance and server capacity

4 Anforderungen

Speed matters to crawling as much as to users: Google adjusts how much it crawls a host to its connect time, time to first byte and error rate, and that capacity is shared by every Google crawler. Fast rendering keeps content from timing out.

  1. DEV-PRF-01SollteKeep connect time and time to first byte low and stable under crawler loadAutomatischServer-Logs
  2. DEV-PRF-02SollteMake JavaScript-generated content render quicklyAutomatischEine URL
  3. DEV-PRF-03KannLoad per-session-billed third-party tools only after a user interactionAutomatischEine URL
  4. DEV-PRF-04SollteKeep each HTML response well under 2 MB and put the main content and JSON-LD earlyAutomatischEine URL

AIF14 / 16

AI features (AI Overviews, AI Mode, Gemini)

6 Anforderungen

AI Overviews and AI Mode use the same crawling and the same index as Search, and query fan-out sends generated queries to that index and gets documents back with their snippets. There is no separate AI index, markup or file to build for; the controls for AI features are covered in the indexing controls above.

  1. DEV-AIF-01MussKeep pages indexable and snippet-eligible, the whole technical requirement for AI featuresAutomatischEine URL
  2. DEV-AIF-02SollteSpend no effort on llms.txt, AI text files or AI-specific markup for GoogleAutomatischEine URL
  3. DEV-AIF-03SollteStructure content for readers instead of splitting it into small chunks for AIUnterstütztCrawl
  4. DEV-AIF-04SollteDo not block the AI agents you want as visitorsUnterstütztServer-Logs
  5. DEV-AIF-05KannSet robots.txt policy per AI crawler by its own token, and know that user-triggered fetchers ignore itAutomatischEine URL
  6. DEV-AIF-06KannTry WebMCP to declare the actions a site offers to AI agentsAutomatischRendering

SPM15 / 16

Spam policies and AI-generated content

5 Anforderungen

Google's spam policies cover practices that deceive users or manipulate Search, including its generative AI responses, and several of them are built in code: history manipulation, cloaking, generated page sets and hacked pages. AI is a tool; how its output is used decides whether content is helpful or spam.

  1. DEV-SPM-01VermeidenNever manipulate browser history so that Back does not return users to where they came fromAutomatischRendering
  2. DEV-SPM-02VermeidenDo not generate large sets of low-value pages from templates, feeds or LLM outputUnterstütztCrawl
  3. DEV-SPM-03VermeidenNever serve Googlebot different content from users, and do not build doorway pagesAutomatischEine URL
  4. DEV-SPM-04MussKeep the CMS and plug-ins patched and watch for injected pages and linksUnterstütztCrawl
  5. DEV-SPM-05SolltePublish AI-generated text, images and markup only after human review, and show only real authorsUnterstütztCrawl

MON16 / 16

Testing and monitoring

11 Anforderungen

Search Console shows what Google crawled, rendered, chose as canonical and indexed. Render one URL per template in a headless browser before every release, check it in URL Inspection right after, and watch the reports that reveal crawling, rendering and index selection problems.

  1. DEV-MON-01MussVerify every production host in Search Console before launchUnterstütztGoogle
  2. DEV-MON-02MussRender every template in a headless browser before release and check it in URL Inspection right afterUnterstütztCI
  3. DEV-MON-03SollteWatch the Page indexing report and treat its not-indexed reasons as a work listUnterstütztGoogle
  4. DEV-MON-04SollteMonitor Crawl stats and server logs for verified Googlebot trafficUnterstütztServer-Logs
  5. DEV-MON-05SollteRun recurring rendering checks: raw versus rendered HTML, placeholders and console errorsAutomatischRendering
  6. DEV-MON-06SollteAudit canonical groups with a crawler on a scheduleAutomatischCrawl
  7. DEV-MON-07KannTrack AI feature visibility in the Generative AI performance reportGeführtIhre Website
  8. DEV-MON-08SollteSet up the Search Console bulk data export to BigQuery on large sitesAutomatischGoogle
  9. DEV-MON-09KannAdd the brand's YouTube, Instagram, TikTok and X accounts to Search Console as platform propertiesGeführtIhre Website
  10. DEV-MON-10SolltePlan releases and fixes around Google's processing times, and judge results only after themUnterstütztIhre Website
  11. DEV-MON-11SollteMeasure the time from publishing a URL to Googlebot's first crawl of itAutomatischServer-Logs

Audit

Prüfen Sie es auf Ihrer Website.

Ein Audit prüft eine URL gegen alle 138 Anforderungen und liefert zu jeder einen Befund, mit Quelle. Eine URL entscheidet 66; bei allen übrigen sagt der Befund, welche Quelle Sie verbinden.

URL kostenlos prüfen