Skip to content
Agentmart
Submit a tool

google-ranking-appearance

Practical guide to Google search ranking and appearance: title links, snippets, structured data, rich results, images, videos, Discover, and local features.

Skill by MathiasPaulenko

IndexedMIT★ 2
Write a review

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-ranking-appearance

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.

We use your email only for this newsletter. Privacy

About

Practical guide to Google search ranking and appearance: title links, snippets, structured data, rich results, images, videos, Discover, and local features.

Use cases: data

No 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-ranking-appearance

What's inside

Skill name
google-ranking-appearance
Description
Practical guide to Google search ranking and appearance: title links, snippets, structured data, rich results, images, videos, Discover, and local features.
License
MIT
Instructions
535 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • body: 535 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 Ranking and Search Appearance

## Description

This skill covers the *Ranking and search appearance* section of Google Search Central. It explains how to influence how a site appears in Google Search results: from title links and snippets to images, videos, structured data, rich results, Google Discover, local features, and page experience.

> 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 asks how to influence the appearance of search results.
- The user wants to optimize title links or meta descriptions.
- The user needs guidance on structured data and rich results.
- The user wants to optimize images or videos for Google Search.
- The user needs to understand page experience and Core Web Vitals.
- The user wants to appear in Google Discover or local results.
- The user asks about featured snippets, favicons, sitelinks, site names, or publication dates.

### Input

- A specific appearance feature or search result type.
- Optional: a URL, HTML, or structured data markup to review.

### Output

- A structured answer with direct links to the relevant Google Search Central pages.
- Implementation guidance, concrete examples, and common mistakes to avoid.

---

## Core concepts

### 1. Search appearance overview

Search appearance is the way Google presents web pages in search results. It includes the basic title link and text snippet, plus enhanced formats such as images, videos, rich results, favicons, site names, sitelinks, featured snippets, and feed-style surfaces such as Google Discover and AI Overviews.

A site owner can influence appearance by providing clear, accurate, and well-structured information. The most common mistakes are treating appearance features as isolated tricks, ignoring page experience, or adding structured data that is not visible to users.

How to influence it:

1. Publish crawlable, renderable content with important text visible in the HTML.
2. Use structured data that matches the main purpose of the page.
3. Optimize the assets that appear in search results: the `<title>` element, the `<meta name="description">` tag, images, videos, and the favicon.
4. Monitor results with Search Console: the Performance, Rich Results, and URL Inspection reports.

### 2. Title links

A title link is the clickable title shown for a search result on Google Search, Google News, and other Google properties. Google creates title links automatically from sources such as the `<title>` element, visible headings, `og:title` meta tags, and anchor text from other sites. Because the title link is usually the first thing a user reads, it strongly influences click-through rates and relevance.

**How to implement**

1. Include a `<title>` element on every page.
2. Write descriptive and concise text. Avoid vague descriptors such as "Home" or "Profile".
3. Avoid keyword stuffing, such as repeating "Foobar, foo bar, foobars," which looks spammy.
4. Avoid boilerplate text replicated across many pages, such as "Cheap products for sale" on every product page.
5. Brand titles concisely. On most pages place the site name at the beginning or end with a delimiter: `<title>ExampleSocialSite: Sign up for a new account.</title>`.
6. Make the main title visually prominent, for example by placing it in the first visible `<h1>` element.
7. Use the same language and writing system as the primary content, and update the `<title>` when the content changes.

A common issue is an outdated title: a university page with `<title>2020 admissions criteria - University of Awesome</title>` but a visible heading of "2021 admissions criteria" may have its title link replaced by the heading. The fix is to update the `<title>` to match the current content.

| Common issue | Solution |
| --- | --- |
| Half-empty `<title>` | Complete the `<title>` with the main topic. |
| Outdated `<title>` | Update the `<title>` whenever the page is updated. |
| Inaccurate `<title>` | Make the `<title>` reflect the actual page content. |
| Boilerplate `<title>` | Make each title specific to the page. |
| No clear main title | Make the main heading the most prominent on the page. |
| Mismatched language | Match the `<title>` to the primary content language. |

**Common mistakes**

- Using vague or identical `<title>` elements across many pages.
- Keyword stuffing in titles.
- Writing the `<title>` in a different language or script than the visible content.

### 3. Snippets

A snippet is the descriptive text shown below the title link. Google primarily creates snippets from page content, but it may also use the `<meta name="description">` tag when that gives a more accurate description. Snippets are query-specific, and a good snippet helps users decide whether to click.

**How to implement**

1. Write a unique `<meta name="description">` for every page.
2. Make the description informative and relevant. Include details such as author, date, price, or location. For example: `<meta name="description" content="Written by A.N. Author, Illustrated by V. Gogh, Price: $17.99, Length: 784 pages">`.
3. Generate descriptions programmatically for large sites, as long as the output is human-readable and varied.
4. Keep descriptions truly descriptive. Do not use long lists of keywords or generic text.
5. Place important content where it is immediately visible, because deep-link snippets work best when content is not hidden behind tabs or accordions.
6. Use `nosnippet` to prevent any snippet, `max-snippet:[number]` to limit length, or `data-nosnippet` to hide specific text.

A good snippet for a sewing supplies shop is `<meta name="description" content="Get everything you need to sew your next garment. Open Monday-Friday 8-5pm, located in the Fashion District.">` instead of a simple list of keywords.

**Common mistakes**

- Relying only on the meta description and ignoring the visible page content.
- Using the same description on every page.
- Writing descriptions that are too short, too vague, or stuffed with keywords.

### 4. Structured data and rich results

Structured data is a standardized format for describing a page and classifying its content. It helps Google understand the meaning of the page and can enable rich results, which are search results with enhanced features such as star ratings, images, prices, and event details. Google case studies show measurable increases in click-through rate for sites that implement structured data correctly.

**How to implement**

1. Choose the right schema.org type for the main content, such as `Article`, `Recipe`, `Event`, `Product`, `LocalBusiness`, `Organization`, `Video`, or `JobPosting`.
2. Use a supported format. Google supports JSON-LD (recommended), Microdata, and RDFa. JSON-LD is usually easiest and can be injected dynamically with JavaScript.
3. Include all required properties for the type. Items missing required properties are not eligible for rich results.
4. Add recommended properties when they are accurate and complete. It is better to provide fewer complete properties than many incomplete ones.
5. Put the structured data on the page it describes. Do not create blank pages just for structured data, and do not mark up information that is not visible to users.
6. Test the markup with the [Rich Results Test](https://search.google.com/test/rich-results?hl=en). After deployment, monitor the Rich result status reports in Search Console.
7. Follow the general structured data guidelines and the specific feature guidelines. Violations can lead to manual actions and loss of rich result eligibility.

A recipe page can include JSON-LD such as:

```html
<script type="application/ld+json">
{
  "@context": "https://schema.org/",

From MathiasPaulenko/ai-toolkit, MIT.

More from MathiasPaulenko/ai-toolkit

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
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from MathiasPaulenko

Cite this page

google-ranking-appearance skill. Agent Mart. https://agentmart.dev/skills/mathiaspaulenko-google-ranking-appearance (last updated 2026-10-24)