google-seo-fundamentals
Practical guide to Google Search SEO fundamentals: Search Essentials, technical requirements, spam policies, helpful content, generative AI guidelines, and…
Skill by MathiasPaulenko
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/mathiaspaulenko-google-seo-fundamentals
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: writing, marketing
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/google-seo-fundamentals
What's inside
- Skill name
google-seo-fundamentals- Description
- Practical guide to Google Search SEO fundamentals: Search Essentials, technical requirements, spam policies, helpful content, generative AI guidelines, and site maintenance.
- License
- MIT
- Instructions
- 543 lines in SKILL.md · view on GitHub
Agent Skills spec issues
- body: 543 lines (spec recommends under 500)
Files (3)
- SKILL.md
- google-search-central-summaries.md · references/
- google-search-central-toc.md · references/
SKILL.md (first lines)
# Google SEO Fundamentals ## Description This skill covers the *SEO fundamentals* section of Google Search Central. It explains how Google Search works, what it takes to appear and perform well, how to create people-first content, the role of generative AI, and how to maintain a site's SEO over time. > The supporting English summaries for this skill are in [`references/google-search-central-summaries.md`](references/google-search-central-summaries.md). ## Usage ### When to invoke - The user wants to understand how Google Search works (crawling, indexing, serving). - The user asks about the basic requirements to appear on Google. - The user needs guidance on creating useful, reliable, people-first content. - The user asks about Google's spam policies and what to avoid. - The user wants to optimize for generative AI features in Google Search. - The user is evaluating whether to hire an SEO specialist or use third-party SEO tools. ### Input - A specific question, page, or topic from the *SEO fundamentals* section of Google Search Central. - Optional: a URL or content the user wants to review against Google's fundamentals. ### Output - A concise, structured answer with direct links to the relevant Google Search Central pages. - Actionable next steps and common pitfalls to avoid. --- ## Core concepts ### 1. Google Search Essentials The [Google Search Essentials](https://developers.google.com/search/docs/essentials?hl=en) are the core rules that make web-based content eligible to appear and perform well on Google Search. They are organized around three pillars: technical requirements, spam policies, and key best practices. Think of them as the baseline contract between your site and Google. Meeting the Essentials does not guarantee a top ranking, but violating them can prevent a page from appearing at all. The first pillar, [technical requirements](https://developers.google.com/search/docs/essentials/technical?hl=en), covers the bare minimum Google needs in order to crawl, index, and serve a page. The second, [spam policies](https://developers.google.com/search/docs/essentials/spam-policies?hl=en), lists behaviors and tactics that can cause a page or an entire site to rank lower or be removed. The third, key best practices, describes the main things that can improve how your site appears in Search. All three pillars work together. A technically perfect page that violates spam policies will still fail, and a high-quality page that Google cannot access will not be shown. Importantly, appearing in Google Search is free. Google does not accept payment to crawl a site more often or to rank it higher. Any claim to the contrary should be treated as a warning sign. #### Minimum technical requirements Google needs only a few technical things from a web page. Most sites that are built normally already pass these requirements without extra work. However, it is worth checking them deliberately because a single misconfiguration can make an entire page invisible. 1. Googlebot must not be blocked. Google only indexes pages that are publicly accessible and that do not block Google's crawler, Googlebot. If a page requires a login, Googlebot cannot crawl it. If `robots.txt` prevents access, the page is unlikely to appear in Search results. To verify access, use the URL Inspection tool in Search Console or the robots.txt tester. 2. The page must work, meaning that Google receives an HTTP `200 (success)` status code. Client errors such as `404` and server errors such as `500` are not indexed. A page that looks fine to a user but returns an error status code to Googlebot will not be indexed. Test the HTTP status with Search Console, a browser network tab, or a command-line tool such as `curl`. 3. The page must contain indexable content. The textual content should be in a file type that Google Search supports, such as HTML, and it must not violate spam policies. In addition, the content should be available without requiring the user to run unsupported plugins or to interact with the page in ways a crawler cannot replicate. A common point of confusion: `robots.txt` blocks crawling, but a URL may still appear in search results if it is linked from elsewhere. To tell Google not to index a page at all, use a [`<meta name="robots" content="noindex">`](https://developers.google.com/search/docs/crawling-indexing/block-indexing?hl=en) tag or an equivalent `X-Robots-Tag` and allow Google to crawl the URL. #### Major spam policies to avoid Google's [spam policies](https://developers.google.com/search/docs/essentials/spam-policies?hl=en) apply to all web search results. Violations can lead to manual actions, ranking demotions, or removal from the index. The following list is not exhaustive, but it covers the most common policy areas that site owners encounter. - **Cloaking** means presenting different content to users and search engines with the intent to manipulate rankings or mislead users. An example is showing a page about travel destinations to search engines while showing discount-drug content to human visitors. Paywalls and content gating are not considered cloaking if Google can see the same content that any person with access would see and if you follow the [Flexible Sampling guidance](https://developers.google.com/search/docs/appearance/flexible-sampling?hl=en). - **Doorway abuse** is the creation of pages that rank for specific, similar queries but funnel users to a single intermediate or final destination. Examples include multiple near-duplicate sites with slight URL or homepage variations, many region- or city-targeted domain names that all lead to the same page, or pages that are closer to search results than to a clearly defined, browseable hierarchy. - **Expired domain abuse** happens when someone buys an expired domain and republishes low-value content primarily to borrow the domain's established signals. Examples include affiliate content on a domain previously used by a government agency, or casino content on a former elementary-school site. - **Hacked content** is any content placed on a site without permission, often through code injection, page injection, or malicious redirects. If a site is hacked, attackers may use cloaking to hide the attack from the site owner. Site owners should follow Google's guidance on fixing and avoiding hacked sites. - **Hidden text and link abuse** means placing content on a page solely to manipulate search engines and not to be easily viewable by people. Examples are white text on a white background, text positioned off-screen with CSS, font size or opacity set to zero, or links hidden behind a single small character. Not all hidden content is abusive: accordions, tabs, sliders, and screen-reader-only text that improves user experience are generally acceptable. - **Keyword stuffing** is filling a page with keywords or numbers in an attempt to manipulate rankings, often in lists or groups that appear unnaturally or out of context. An example is a block of text that repeats the same phrase so often it sounds robotic. It is also keyword stuffing to list cities or phone numbers without substantial added value. - **Link spam** is the creation of links to or from a site primarily to manipulate rankings. Buying or selling links, excessive link exchanges, automated link-building programs, requiring links in terms of service, advertorials that pass ranking credit, low-quality directory links, and keyword-rich links in widgets, footers, or forum signatures are all examples. Links that are part of normal advertising or sponsorship are acceptable if they are qualified with `rel="nofollow"` or `rel="sponsored"` on the `<a>` tag. - **Scaled content abuse** is the mass production of unoriginal content that provides little to no value to users, regardless of how it is created. Using generative AI or automation to produce many pages without adding value, scraping feeds or results to generate pages, stitching content from different sources, or creating multiple sites to hide the scaled nature of the work all fall under this policy. - **Scraping** is taking content from other sites, often through automated means, and hosting it to manipulate rankings. Republishing content without original value or citation, copying and lightly modifying another site's content, or building a site dedicated to embedding other people's media without substantial added value are all examples. - **Site reputation abuse** is publishing third-party content on a host site mainly because that host site has already earned strong ranking signals. The test is whether the content would rank better on the established host than it could on its own. Coupons, advertorials, and affiliate links can be legitimate if they are clearly presented and treated appropriately, but third-party content that is hosted primarily to manipulate rankings can violate this policy. #### Key best practices that influence appearance While the technical requirements are the floor, the following practices are the main things Google recommends for improving how your site appears in Search. - Create [helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content?hl=en). This is the single most important practice. Content should be created to help users, not to manipulate rankings. - Use words that people would naturally search for and place them in prominent, descriptive locations. These include the `<title>` element, the main heading of the page, image `alt` text, and the visible text of links. This helps Google understand what the page is about and helps users decide whether to click. - Make your links crawlable. Google discovers pages primarily by following links. If important pages are only reachable through forms, JavaScript events, or non-crawlable navigation, Google may never find them. - Tell people about your site through legitimate promotion, community engagement, and offline materials. Word-of-mouth discovery remains one of the most effective and lasting ways to build an audience. - Follow best practices for [images](https://developers.google.com/search/docs/appearance/google-images?hl=en), [videos](https://developers.google.com/search/docs/appearance/video?hl=en), [structured data](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data?hl=en), and [JavaScript](https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics?hl=en) so that Google can understand every part of the page. - If you have content that should not appear in Search, use the correct method for [controlling how your content appears](https://developers.google.com/search/docs/crawling-indexing/control-what-you-share?hl=en). Do not rely on hope or on obscure tricks. **Concrete example** A small bakery launches a page for wedding cakes. The owner places the target keywords in the `<title>` element, the main heading, and image `alt` attributes; the URL is `https://www.example.com/wedding-cakes`; the page returns HTTP 200; the page is linked from the site navigation; and the text describes the bakery's real experience, pricing, and service area. The page is not blocked by `robots.txt` or `noindex`. Because it meets the technical requirements, avoids spam tactics, and follows key best practices, it is eligible to appear when people search for wedding cakes in that area. **Common mistakes** - Believing that paying for submission or inclusion will improve rankings, or accidentally allowing staging or test sites to be indexed. - Using `robots.txt` to try to remove a page from search results, or stuffing footers with city names and phone numbers that add no real value. ### 2. How Google Search works Google Search is a fully automated search engine. It uses software known as [web crawlers](https://developers.google.com/search/docs/crawling-indexing/googlebot?hl=en) to explore the web regularly, find pages, and add them to the [Google index](https://developers.google.com/search/docs/fundamentals/how-search-works?hl=en). The vast majority of pages listed in Google's results are not manually submitted. They are found and added automatically as Google crawls the web. Understanding the three stages of Search is essential for debugging problems. If a page is not appearing, the cause is usually at one of these stages. #### The three stages 1. **Crawling**: Google downloads text, images, and videos from pages it has found on the internet. Googlebot discovers URLs in several ways. Some pages are known because Google has already visited them. Others are discovered when Google extracts a link from a known page to a new page, such as when a category page links to a new blog post. Still others are discovered when the site owner submits a [sitemap](https://developers.google.com/search/docs/crawling-indexing/sitemaps/overview?hl=en) listing important pages. Once Googlebot discovers a URL, it may visit the page to find out what is on it. Googlebot uses an algorithmic process to determine which sites to crawl, how often, and how many pages to fetch. It also tries not to crawl a site too fast, and it may slow down in response to server errors such as `500`. During the crawl, Google renders the page and runs JavaScript using a recent version of Chrome. This is important because many sites rely on JavaScript to bring content into the page. If the JavaScript is blocked or unsupported, Google may not see the content. 2. **Indexing**: After a page is crawled, Google tries to understand what it is about. This stage includes processing and analyzing the textual content and key content tags and attributes, such as `<title>` elements, `alt` attributes, images, and videos. Google also determines whether a page is a duplicate of another page and selects a [canonical](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls?hl=en) version to represent a group of similar pages.
From MathiasPaulenko/ai-toolkit, MIT.
More from MathiasPaulenko/ai-toolkit
- 0.583score
BiDiWave Cross-Browser
MathiasPaulenko
Cross-browser testing with bidiwave using the W3C WebDriver BiDi protocol.
SkillAFreshness: A★ 2Claude Code +9 - 0.581score
Skill Name
MathiasPaulenko
What this skill does and when to use it
SkillAFreshness: A★ 2Claude Code +9 - 0.559score
google-crawling-indexing
MathiasPaulenko
Practical guide to Google crawling and indexing: sitemaps, robots.txt, meta tags, canonical URLs, redirects, JavaScript, removals, and crawler management.
SkillBFreshness: B★ 2Claude Code +9 - 0.550score
google-seo-monitoring
MathiasPaulenko
Practical guide to Google SEO monitoring and debugging: Search Console, Google Analytics, Google Trends, search operators, traffic drops, security, spam, and…
SkillBFreshness: B★ 2Claude Code +9 - 0.550score
google-ranking-appearance
MathiasPaulenko
Practical guide to Google search ranking and appearance: title links, snippets, structured data, rich results, images, videos, Discover, and local features.
SkillBFreshness: B★ 2Claude Code +9 - 0.542score
CDPWave Testing
MathiasPaulenko
Write browser automation tests with cdpwave at the CDP level.
SkillBFreshness: B★ 2Claude Code +9 - 0.542score
CDPWave Debugging
MathiasPaulenko
Advanced debugging with cdpwave.
SkillBFreshness: B★ 2Claude Code +9 - 0.542score
BiDiWave Network Interception
MathiasPaulenko
Network interception with bidiwave.
SkillBFreshness: B★ 2Claude Code +9 - 0.504score
appium-mobile
MathiasPaulenko
Mobile automation with Appium: iOS and Android, gestures, device farms (BrowserStack, Sauce Labs), parallel execution, and CI/CD.
SkillCFreshness: C★ 2Claude Code +9 - 0.504score
jmeter-load-testing
MathiasPaulenko
Load and performance testing with Apache JMeter.
SkillCFreshness: C★ 2Claude Code +9 - 0.504score
db2-oracle
MathiasPaulenko
Enterprise database development for IBM DB2 and Oracle.
SkillCFreshness: C★ 2Claude Code +9 - 0.504score
ebook-writer
MathiasPaulenko
Comprehensive ebook creation skill covering outlining, chapter writing, editing, formatting, and marketing.
SkillCFreshness: C★ 2Claude Code +9
Signals
- Stars
- 2
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Aug 21, 2026 (2 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/MathiasPaulenko/ai-toolkit
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from MathiasPaulenko
- 0.629score
WaveXisMCP
MathiasPaulenko
220 browser automation tools for Chrome, Edge, and Firefox via CDP + BiDi.
ConnectorAFreshness: ALocal★ 3↓ 92/wkClaude Code +5 - 0.583score
BiDiWave Cross-Browser
MathiasPaulenko
Cross-browser testing with bidiwave using the W3C WebDriver BiDi protocol.
SkillAFreshness: A★ 2Claude Code +9 - 0.581score
Skill Name
MathiasPaulenko
What this skill does and when to use it
SkillAFreshness: A★ 2Claude Code +9 - 0.559score
google-crawling-indexing
MathiasPaulenko
Practical guide to Google crawling and indexing: sitemaps, robots.txt, meta tags, canonical URLs, redirects, JavaScript, removals, and crawler management.
SkillBFreshness: B★ 2Claude Code +9 - 0.550score
google-ranking-appearance
MathiasPaulenko
Practical guide to Google search ranking and appearance: title links, snippets, structured data, rich results, images, videos, Discover, and local features.
SkillBFreshness: B★ 2Claude Code +9 - 0.550score
google-seo-monitoring
MathiasPaulenko
Practical guide to Google SEO monitoring and debugging: Search Console, Google Analytics, Google Trends, search operators, traffic drops, security, spam, and…
SkillBFreshness: B★ 2Claude Code +9
Cite this page
google-seo-fundamentals skill. Agent Mart. https://agentmart.dev/skills/mathiaspaulenko-google-seo-fundamentals (last updated 2026-10-24)