Research Guides
Audit the Site Name Separately from the Page Title
“The wrong name appears in search” is not yet a precise editing task. The complaint might refer to the name of the website, the title of a particular article or a word in the descriptive snippet. Identify the element before changing a template across the entire site.
This is a manual research and implementation-review worksheet for a site you are authorized to inspect. It does not describe a Colquhoun.shop search-management feature or promise that a preferred name will be displayed.
1. Capture the observation before diagnosing it
Save the result URL, query, observation date and a screenshot showing the specific wording in context. Label the disputed element in your record. A message saying only “change the search title” can lead an editor to modify the wrong field.
Google distinguishes the site name from each page's title link. Its site-name system is automated, and homepage WebSite structured data indicates a preference rather than a guaranteed display choice. Google: Provide a site name to Google Search
Keep the observation separate from the proposed correction. A screenshot establishes what appeared in that check; it does not by itself explain why Google selected the wording.
2. Agree on the identity being represented
Ask the content owner for the approved public site name and any genuinely used short form. Record the source of that decision. Do not invent an acronym or replace the brand with a search phrase merely because it looks more descriptive.
Google supports site names at the domain or subdomain level, not for individual subdirectories. Its guidance recommends consistent homepage naming and putting the relevant structured data on the domain or subdomain homepage. Existing WebSite data should be updated in the same node rather than unnecessarily adding another block.
Before assigning implementation, write down the exact homepage being reviewed. This prevents a request concerning a whole site from turning into an unrelated edit to one article's metadata.
3. Build a conflict ledger
Inspect visible homepage branding and the relevant metadata without changing them yet. For each occurrence, record the current wording, its location, the intended wording and the person responsible. Distinguish genuine conflicts from useful page-specific descriptions.
In an invented example, a publication has adopted “Cedar Research,” while its homepage structured data still says “Cedar Notes.” The owner confirms the new name, but a historical article intentionally discusses the old project. The homepage discrepancy needs review; the historical reference does not automatically need a global replacement.
Use a narrowly scoped change list. Avoid replacing every occurrence of the old text across source files, archived quotations and unrelated organizations without inspecting context.
4. Separate implementation evidence from search evidence
After an authorized update, retrieve the public homepage and confirm the agreed wording and intended structured-data node are present. Check that the page still renders, links still work and unrelated metadata remains intact. Save the before-and-after record with the deployment reference.
Google says site names are not supported by the Rich Results Test; its guidance instead points to a schema testing tool for markup validation and URL Inspection for how Google sees the page. Passing a syntax check is not proof that the chosen name has appeared in search.
5. Close only the part you actually verified
- Observed issue: result element, wording and check date.
- Approved identity: site name, homepage and owner decision.
- Conflicts: exact occurrences requiring correction.
- Published evidence: public page and markup checks.
- Search follow-up: later observation, still pending or unchanged.
A defensible completion note might say “homepage naming now matches the approved identity; search display not yet confirmed.” That is more useful than declaring the problem solved immediately after saving a field.