SEO & Search

Google Site Names for B2B Websites: Separate the Brand Label From the Page Title

The screenshot says the brand is wrong. The editor changes a service page's title. The next screenshot still shows the same brand label.

Start by naming the field under review.

A site-name review needs a homepage, a requested identity, and an observation record. Put those beside the search result before assigning an edit.

The worksheet below is a proposed review method. The business and all search observations are fictional. Use the example to separate a decision about identity from a change to source text and a later check of search appearance.

Identify the Label Before Opening the CMS

Google distinguishes the site-wide name from each page's title link. Selection is automated. Homepage WebSite data is its strongest preference signal; visible naming, headings, title, and og:site_name also matter. Names should be distinctive, concise, accurate, and consistent. Google's site-name guidance establishes those boundaries.

For a fictional consultancy, put four different objects in the review record:

Object Synthetic value Review question
Observed site name Alder Operations Is this the requested public identity?
Observed page title link Supplier Intake Review Does this describe the destination page?
Domain alder.example.com Which website are we inspecting?
Organization identity Alder Operations Advisory LLC Which business does the owner identify?

These invented strings describe different things. Keep them in separate columns even when some happen to match.

Suppose the owner requests “Alder Advisory.” Ask which field should carry that text. A request to change the organization name across contracts is outside this worksheet. A request to correct one service heading needs a page review. A request about the site's search label belongs here.

Keep the screenshot intact. Cropping away the destination can remove the context needed to identify the affected site. Record the query and date beside it. Treat the capture as one observation, with its own device and language settings.

Use the title-link diagnosis worksheet when the disputed words belong to an individual page's link. Do not send the same ambiguous screenshot to two owners with different assignments.

Define the Site Boundary

Google supports one name per domain or subdomain, not per subdirectory. It generally treats www and m variants as equivalent. The relevant homepage is the root URL. Duplicate homepages need matching structured data. The technical guidance defines that scope.

For the proposed review, draw a small inventory before touching a template. Give every candidate homepage its own row. Copy the actual address from the reviewed environment. Mark whether the row represents a separate site, a duplicate, or an unresolved configuration.

In the fictional inventory, alder.example.com/ is the consultancy homepage. /resources/ is a section within it. learn.alder.example.com/ is listed as a separate teaching site with an owner still to be confirmed.

The editor wants the resources section to read “Alder Research.” Preserve that request in the record, but assign it to section navigation and page content. Keep the site-name request attached to the homepage being reviewed.

Do not reorganize the website to satisfy a naming worksheet. Moving material to another host creates a separate architecture decision. State the reader problem first. Ask whether the existing navigation and page wording can answer it.

The inventory should reveal uncertainty, too. If nobody knows whether an alternate homepage redirects, record “redirect behavior unverified.” That gives the developer a concrete question without pretending the inventory is complete.

Compare the Homepage Evidence

Google requires name and the canonical homepage url in homepage WebSite markup. Optional alternateName accepts genuine alternatives in preference order. Update the existing node rather than creating a competing one. The homepage must be crawlable. These are documented inputs, not display commands.

Build the editorial comparison around those fields. Copy their current values into a worksheet. Put the visible homepage label in the next row. Keep requested text in a separate column so the reviewer can distinguish inspection from proposal.

Here is a fictional proposed node, shown as text for review:

{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Alder Advisory",
  "alternateName": "Alder",
  "url": "https://alder.example.com/"
}

The example does not supply a production implementation. Before using its shape, inspect the website's current output and the system that generates it. Ask the maintainer where an approved change belongs.

For Alder, suppose the header reads “Alder Advisory” while an older metadata field reads “Alder Operations.” Record both strings exactly. Do not silently replace them in your inspection notes.

Ask the brand owner to accept the preferred name and any alternative. A reviewer can check consistency after that choice. A reviewer cannot settle a disputed business identity by choosing whichever string appears most often.

Keep the broader schema review separate from this assignment. This record needs a narrow answer about homepage identity evidence. It does not need a new collection of unrelated schema types.

Work Through a Fictional Change Record

Assume Alder's owner accepts “Alder Advisory” as the requested public name. Every date, inspection, and result in the following table is invented.

Evidence Before review Accepted change Later review record
Visible homepage label Alder Advisory Keep approved wording Same wording confirmed on October 28
Homepage name field Alder Operations Change to Alder Advisory Revised bytes confirmed on October 28
Alternative field Empty Add owner-approved Alder Value confirmed on October 28
Homepage URL field Old preview address Use accepted public homepage Address confirmed on October 28
Crawl access Not examined Assign an access review Still unresolved on October 28
Search appearance Alder Operations on October 27 No direct edit to this observation New observation not yet collected

Read the last two rows before declaring success. The source change has been inspected. Access remains unresolved. No new search observation exists.

A useful status note says: “Homepage naming changes confirmed. Access review assigned. Search appearance pending.” It tells the owner what happened without inventing a result.

Now extend the fictional record. On November 4, the editor captures another result showing “Alder Operations.” Save that observation beside the first. Reopen the homepage and confirm which revision is present. Ask the access owner for the missing evidence.

Do not replace the accepted name again because the new capture looks unchanged. First finish the assigned checks. Repeated edits without an inspection record make it harder to identify which version a later reviewer is comparing.

The table has six evidence rows. Three revised source fields do not equal three observed search improvements. Keep task counts and appearance observations in different totals, or omit totals entirely.

Use a Worksheet With Explicit Unknowns

Copy this proposed worksheet into the website's review document. Use one record per site under review.

Field What to enter
Requested name Exact owner-approved public wording
Supported scope Domain or subdomain under review; excluded sections
Homepage Address and reviewed revision
Visible evidence Header, heading, and other naming text copied separately
Markup evidence Current name, alternatives, URL, and node location
Crawl access Evidence, inspection date, owner, or unresolved status
Proposed change Specific field and accepted replacement
Change evidence Revision, confirmation date, and reviewer
Observation date Query, destination, device, language, and capture date
Unresolved differences Source conflicts, missing checks, or appearance mismatch
Next owner Person responsible for the next unanswered question

Use “not examined” when nobody inspected a field. Use “not present” only after an inspection supports that statement. Those entries call for different follow-up work.

Preserve the exact spelling of the accepted name. If the editor proposes a shorter form, put it in the proposal field. Have the owner accept it before anyone treats it as an established alternative.

Keep business approval and technical confirmation separate. The owner can approve “Alder Advisory” while the developer still needs to find the generating template. Both states belong in the record.

Attach evidence at the level another person can review. A revision identifier and a short excerpt can be more useful than a large screenshot of an entire code file. Keep credentials and private settings out of the review document.

Give Each Unresolved Difference an Owner

For the fictional access gap, assign the website maintainer a concrete question: can the relevant homepage be retrieved under the intended public access configuration?

Ask for the inspected address, date, and result. Keep an ordinary browser load separate from any crawler-specific inspection. Label the method used so the next reviewer knows what the evidence establishes.

For a source conflict, assign the editor the exact strings to reconcile. “Header says Alder Advisory; metadata says Alder Operations” is an actionable issue. “Brand signals are weak” hides the inspection and the decision.

For an identity disagreement, return the choice to the owner. The developer should not decide whether the consultancy presents itself under a personal name, a practice name, or a legal entity name.

The personal brand SEO strategy provides a wider planning context for an individual website. Keep that discussion out of a narrow implementation ticket unless the owner has requested an identity decision.

Close a source correction when its agreed evidence exists. Leave the observation task open until someone captures and records the later appearance. Those tasks can have different owners and completion dates.

Review the Observation Without Inventing a Cause

At the next review, compare the saved result with the current homepage record. Start with what changed and what remains unknown.

If the observed label matches the request, record the match for that capture. Preserve the query, destination, date, and context. Avoid turning one successful observation into a permanent guarantee.

If the label differs, record the exact difference. Check whether the comparison uses the same site and the intended source revision. Revisit incomplete access or naming checks before creating another edit request.

Keep a separate line for explanation. Write “cause not established” when the record cannot support one. An unchanged label does not identify which input drove selection. A changed label does not isolate one edit as its cause.

End the review with a bounded next action: confirm the homepage revision, resolve the named access gap, or collect another dated observation. Give that action an owner. Leave completed source work visible so another person can continue from the evidence.

Keep the label and the evidence together.

Sources

Topic map: AI search and the changing results page

Articles in this cluster, then the 3 clusters that share the most topics with it.

This cluster: AI search and the changing results page

Neighbor: Technical SEO, crawling, and migrations

Neighbor: SEO by industry and location

Neighbor: Search measurement and reporting