Control How Your Site Appears in Google Search Results

Short answer: Google builds each search result line automatically from signals on your page and across the web. You cannot set the title link, the snippet, the site name or the favicon directly, but you can shape every one of them by editing the sources Google reads. This guide maps the parts of a result line, separates what is yours from what is Google's, suggests a way to measure the outcome, and tells you which detailed guide to open for each symptom.

It is written for brand owners, SEO specialists and content editors. Details on Google's help pages can change over time, so check the current pages before you act, and treat no step as a guarantee of a particular appearance.

Anatomy of a Result Line and Who Controls Each Part

A result line is assembled from several separate elements, and each draws on a different source. Fixes aimed at the wrong element rarely work. People rewrite a meta description when the real problem is the title, or edit one article's title when the real problem is the name Google shows for the whole site.

The four visible pieces

• Favicon: the small icon beside the result, defined on your home page.
• Site name: the name shown for the whole site, generated from your home page and references to it across the web.
• Title link: the clickable headline, generated for each page.
• Snippet: the text below the headline, which can change from one query to the next.

A control map

Why the scope matters

Two pieces work at site level and are read from one place, the home page. Two work at page level and are generated for every URL. The practical consequence is simple. If one article shows a strange title, touching your home page markup is pointless. If your brand name shows up wrongly across many results, rewriting individual article titles will not help.

Why two people see two different lines

Google says the snippet for a page may differ by query, so one page can appear with different text for different searches. The Search Console help page for the Performance report adds a related warning: what you see when you search a query yourself may differ from the report, because results depend on the searcher's time, place, device and history. A screenshot from a colleague is therefore a data point, not a verdict.

Where this guide stops

Auditing a whole brand search, including knowledge panels and profiles, is a larger job covered in how to audit your brand SERP. The question here is narrower: where does each piece of a single result line come from, and what can you change?

Titles and Descriptions: What You Set and What Google Chooses

The title link and the snippet are the parts closest to the page, and in both cases Google weighs several signals together instead of reading one tag.

Where title links come from

According to Google's page on influencing title links (Opens in a new tab), title links are generated automatically, taking into account both the content of the page and references to it that appear on the web. The sources it lists are the title element, the main visual title shown on the page, heading elements such as the H1, og:title meta tags, other large and prominent text identified through style treatments, other text on the page, anchor text on the page, text within links that point to the page, and WebSite structured data. The page also says Google cannot manually change the title link for an individual site.

What you can do for titles

• Give every page a title element, and avoid vague labels such as "Home" or "Profile".
• Keep titles descriptive and concise. There is no length limit, but titles are truncated to fit the device width.
• Do not repeat the same words. A few descriptive terms are enough, and repetition looks spammy.
• Make each title distinct. Long titles that vary by one small detail are discouraged.
• Add the site name briefly. On the home page, more descriptive text is reasonable. Elsewhere, put only the site name at the start or end, separated by a delimiter such as a hyphen, colon or pipe.
• Make the main title the most prominent text on the page, for instance a larger font or the first visible H1.
• Write the title in the same language and script as the page's main content.

For the craft of writing titles themselves, see writing SEO titles and meta descriptions. This section is about understanding why Google sometimes ignores yours.

Seven reasons Google rewrites a title

1. Half-empty title: part of it is missing, such as a lone "| Site Name".
2. Obsolete title: a year or similar detail does not match the visible date on a recurring page.
3. Inaccurate title: the title element does not reflect the content, especially on dynamic pages.
4. Micro-boilerplate: several pages on the site share an identical title.
5. No clear main title: several headings carry similar prominence.
6. Language or writing system mismatch: the title does not match the primary content.
7. Duplicate site name: for domain-level site names, Google may drop a repeated site name from the title link.

How snippets are formed

Google's snippet and meta description (Opens in a new tab) page says Google primarily uses the content on the page to determine the snippet automatically. Because the snippet is meant to show the part of the page most relevant to the query, different searches can produce different snippets for the same page. Google may use the meta description instead when it would give users a more accurate description than the page text. The page states there is no limit on meta description length, but snippets are truncated as needed, typically to fit the device width.

Practical meta description rules

• Write a unique description for each page. If time is short, start with the home page and your most popular URLs.
• On news, blog and product pages, include useful details such as author, publication date or price.
• On large database-driven sites, programmatic generation is encouraged, provided the descriptions are human-readable and diverse.
• Avoid strings of keywords. The page says they do not describe the content clearly and are less likely to be shown.
• Summarise the whole page, be specific, and do not repeat the same text across many pages.

The three snippet controls

The nosnippet rule prevents a snippet from being shown for a page. The max-snippet:[number] rule sets a maximum snippet length. The data-nosnippet attribute keeps specific parts of a page out of snippets. The page does not quantify how these affect traffic, so treat any change as an experiment and watch the results in Search Console.

Deep links from snippets

The same page notes that a few habits help the "read more" deep links work: keep content visible without requiring users to expand sections or switch tabs, do not use JavaScript to force the scroll position on load, and do not strip the hash fragment if you modify the URL or use the History API on load.

Example scenario: a tab-heavy product page

Example scenario: a software vendor puts its main explanation inside tabs and accordions, and the snippet Google shows for it is a line from the footer. The editor moves the key explanation into visible text near the top and tightens the page's first paragraph so that it answers the query directly. The meta description stays as it was. The page content, not the tag, was the weak signal.

A decision rule for unexpected titles and snippets

If Google shows a title you did not expect, first check whether one of the seven causes above applies to your page and fix it. If none applies, ask honestly whether the title Google chose fits the query better than yours does. Google's page suggests the Search Central Help Community for feedback. For snippets the same logic holds: make the page itself answer the query clearly, and treat the meta description as a supporting signal, not the main fix.

Site Name and Favicon Signals

These two pieces operate at site level, both are read from the home page, and both need a recrawl before a change shows.

What the site name is

Google's site names (Opens in a new tab) page defines the site name as the name shown for the entire site, separate from per-page title links. Generation is automated and draws on the home page and references to it across the web. WebSite structured data is the main way to state a preference, and the system also considers og:site_name, the title element, heading elements and other home page text. Google cannot manually change an automatically selected name.

The WebSite properties

• name (required): the site's name.
• url (required): the canonical home page of the domain or subdomain.
• alternateName (recommended): one or more alternatives, listed in order of preference.

JSON-LD and microdata both work. The markup must sit on the domain or subdomain root: https://example.com qualifies and https://example.com/de/index.html does not. The home page has to be crawlable. If duplicate home pages exist, such as HTTP and HTTPS or www and non-www, the same markup must appear on all of them, not only the canonical one. If a WebSite node already exists, add the site name properties to it instead of creating a second block.

Naming guidance

• Choose a unique name that reflects the site and does not mislead.
• Keep it concise and commonly recognised, because long names may be truncated on some devices.
• Avoid generic names unless the name is a well-recognised brand.
• Use the name consistently across the home page and other sources.
• Supply alternateName values in case the preferred name is unavailable.

Hard limits

One site name is supported per site, where a site means a domain or subdomain. Subdirectory-level names are not supported, and subdomains starting with www or m are treated as equivalent. The Rich Results Test does not support site names, so validate with a schema testing tool such as the Schema Markup Validator, and use the URL Inspection tool to confirm Google can reach the home page, since robots.txt, noindex or a login requirement can block it.

When the preferred name is not chosen

1. Verify that the WebSite name is your preferred name, that there are no structured data errors and that other home page sources use the same name.
2. Confirm you are not attempting a subdirectory-level name.
3. Check redirects: if the page redirects to a page Googlebot can see, the site name reflects the redirect target.
4. Use the same site name on the HTTP and HTTPS versions.
5. After updating the markup, allow time for recrawling.

If that fails, Google's fallbacks are, in order: add an alternateName, which the system strongly considers; add the lowercase domain or subdomain as the last alternateName entry; and, as a last resort, set the lowercase domain as the name value.

Defining the favicon

The favicon for search results (Opens in a new tab) page says to add a link element to the home page head. The rel value icon is the standard, shortcut icon is an older alternative that is still supported, and apple-touch-icon and apple-touch-icon-precomposed are also supported. The href can be relative or absolute, and the file can be hosted off your site, for example on a CDN.

Favicon rules

• One favicon per hostname. news.example.com and example.com can each have one; a subdirectory such as example.com/news cannot.
• Googlebot must be able to crawl the home page and any redirects to the page that specifies the favicon, and Googlebot-Image must be able to crawl the icon file. Neither may be blocked by robots.txt or other means.
• The icon should represent your brand.
• It must be square (1:1) and at least 8x8 pixels. The page recommends a favicon larger than 48x48 pixels for display quality and does not require a multiple of 48.
• Supported formats are BMP, GIF, ICO, PNG, JPEG, PPM and TIFF.
• The icon's URL should not change frequently.
• Google does not show favicons it considers inappropriate, such as pornography or hate symbols, and replaces them with a default icon.

Even when every guideline is met, the page says a favicon may not appear.

Multilingual and multi-domain sites

Because the site name is defined per domain or subdomain, a site that serves its Turkish and English content from subdirectories of one domain has a single site name, and a different name per subdirectory is not supported. With separate subdomains, each home page carries its own markup, and if a subdomain's home page has none, the domain-level name may be used instead. The same hostname rule applies to the favicon. A bilingual brand keeps things simple by using one spelling of its name everywhere and not translating it.

Waiting for the change to show

After you update the home page, Google must recrawl and process it. The title link, site name and favicon pages all say this can take from a few days to a few weeks. You can ask for the home page to be indexed with the URL Inspection tool.

Home page checklist

1. WebSite markup is on the home page with a correct name and url, plus an alternateName.
2. The same markup is present on every duplicate of the home page.
3. The favicon link element is in the home page head, and the icon is square and large enough.
4. robots.txt blocks neither the home page nor the icon file.
5. The name matches in the home page title, og:site_name and your external profiles.
6. After the update, indexing was requested for the home page and enough time has passed.

Measuring Appearance in Search Console and by Hand

Judging a result line by eye is quick and misleading. Measure with two layers: Search Console for aggregate data and manual checks for individual samples.

The Performance report

The Performance report (Opens in a new tab) shows clicks, impressions, click-through rate and average position. Its table tabs cover Queries, Pages, Countries, Devices, Search appearance and Dates, and a search type filter covers Web, Image, Video and News among others. The default view is the past three months and the date range can be changed. Interface labels may differ if you use a language other than English.

Reading it without fooling yourself

If you rewrote a title or description, look at that page's click-through rate. CTR alone does not prove the new title caused a change, because position, query mix and seasonality move as well. Compare equal-length periods before and after and keep to the same group of queries. The help page notes that chart totals can differ from table totals because the chart aggregates by property while the Pages and Search appearance tabs aggregate by page, and that the newest data may be preliminary and can change over the next few hours.

Manual spot checks

1. Search for your brand and for a few page titles, on desktop and on mobile.
2. Run the home page through the URL Inspection tool and check the crawled version and redirects.
3. View the source and confirm the title, meta description, og:title, og:site_name and favicon link elements.
4. Test the WebSite markup in the Schema Markup Validator.
5. Confirm robots.txt and noindex status.
6. Record findings with date and device in a table.

What manual search cannot tell you

Results vary by person, place, device and history, so a single screenshot is not proof. Looking from several devices and sessions is more reliable, and Search Console remains the reference. Do not expect to see a change straight away, either, since recrawling and processing can take days to weeks.

A monitoring plan

Keep a change log

Write down every title, description and markup change with its date, page and reason. Without a log you will not know in a month what to blame for a CTR shift. Many forces act on a result line at once, including query mix, season, competing results and the format Google picks. A log helps you separate them without proving cause and effect, and changing a small batch at a time makes it easier to see which change mattered.

Which Fix Guide to Open for Which Symptom

Start from the symptom, identify the piece, correct the signal and wait for a crawl cycle.

Symptom to guide

Order of repair

1. Decide whether the problem is at site level or page level.
2. For site level, fix the home page: WebSite markup, favicon link element and crawl access.
3. For page level, fix the title element, H1, description and consistency of the page content.
4. Publish, request indexing of the home page where relevant, and allow time.
5. Verify with Search Console data and manual checks.

Mistakes that waste time

• Trying to repair a site name by editing individual article titles.
• Treating the meta description as a magic fix and neglecting page content.
• Expecting a result a day after a change.
• Putting WebSite markup on subdirectory pages.
• Changing the favicon file address often or blocking it in robots.txt.
• Assuming every search shows the same line.

Related guides: Why Google Rewrites Your Title Link and What to Do.

Conclusion

A search result line has four pieces, each with its own source and its own owner. The favicon and the site name are read from the home page, while the title link and the snippet are generated for each page. You cannot set any of them directly. You communicate your preference by keeping the signals Google reads clear, consistent and crawlable. When something looks wrong, identify the piece and the level first, correct the relevant signal, allow a crawl cycle, then confirm in Search Console and by hand. Details on Google's help pages can change, so check the current pages before you act.

If you want titles, descriptions and page copy produced consistently, you can look at the content writing service on Akua Adforce; scope and terms are listed on the product page.

Frequently Asked Questions

Why did Google change the title shown in search results?

Google generates title links automatically and uses the title element, headings such as the H1, og:title, anchor text and other signals. A different title can be produced when yours is half-empty, obsolete, inaccurate, shared across many pages or mismatched with the page's language. Check those causes first and fix any that apply.

Will my meta description appear exactly as written?

There is no guarantee. Google primarily uses page content to build the snippet and uses the meta description only when it gives a more accurate description than the page text. The snippet can also vary by query. Writing a unique, descriptive meta description is still recommended.

Why does my site name look wrong or show the domain?

Site names are chosen automatically from signals such as WebSite structured data, og:site_name, the title element and headings on the home page. Check that the markup is on the root home page, that the name is used consistently, and that an alternateName is present. After updating, recrawling can take days to weeks.

Why is my favicon missing in search results?

Check the link rel icon element in the home page head, that the icon is square and at least 8x8 pixels, and that Googlebot and Googlebot-Image are not blocked. Google's documentation says a favicon may not appear even when every guideline is met.

Can I set a different site name or favicon for a subdirectory?

No. Site names apply to a domain or subdomain, and subdirectory-level names are not supported. A favicon is also limited to one per hostname, so a path such as example.com/news cannot have its own.

How long until a change shows in search results?

Google must recrawl and process the page. The title link and site name pages say this can take from a few days to a few weeks. You can request indexing of the home page with the URL Inspection tool, but timing is not guaranteed.