Public register of verified sites

The label appears on the proof card; the public surface does not define its verification method or scope.

That is the complete public meaning available from the card itself. Do not expand the label into a claim about how TrustGrowth authenticated an account, which property was checked, when a check occurred, or what data access exists behind the page. Those details are not defined on the public surface. The label also does not show that Google reviewed TrustGrowth, endorsed the score, audited the site, or confirmed any SEO result.

Google Search Console uses its own, separately documented concept of ownership verification. In Search Console, verification is the process used to prove ownership of a property before gaining owner access. Google explains that process in Verify your site ownership and defines a Search Console property in Add a website or platform property. Those Google definitions help readers understand Google’s product, but they do not add meaning to TrustGrowth’s public label.

Keep the boundary strict when quoting or summarizing a card. You may report that the card displays GSC verified. You should not translate the label into a claim that the public page has independently established ownership, access level, data completeness, data accuracy, or recency. You should also avoid treating it as evidence of future performance. A displayed label and an outcome are different facts.

Read each visible number by its name and context. Clicks, impressions, click-through rate, and average position are Search Console performance metrics when the proof surface identifies them that way. A TrustGrowth score, audit finding, content assessment, E-E-A-T assessment, or technical assessment is a TrustGrowth evaluation. The two groups can appear near each other without measuring the same thing.

Google defines an impression as an instance in which a user saw, or potentially saw, a link to a site on a supported Google surface. Google generally counts a click when a user follows a result to a page outside Google. The detailed rules vary by result type and aggregation method, so use Google’s current definitions rather than an informal shorthand. The official definitions are adjacent here: What are impressions, position, and clicks? and Performance report: About the data.

A TrustGrowth score is not a Search Console metric. It is a platform evaluation shown by TrustGrowth. Do not describe it as a Google score, and do not assume that its scale or update timing matches a Search Console report. Likewise, a TrustGrowth issue count is not a count of Search Console warnings unless the specific surface explicitly says so.

This distinction matters when comparing values over time. Search Console performance data describes activity recorded under Google’s reporting rules. A TrustGrowth evaluation describes the site under TrustGrowth’s current checks and scoring logic. One value may change while the other stays still. That difference is not automatically an error, and it is not automatically evidence that one caused the other.

When a label is unclear, quote the visible label and stop at what the surface supports. Do not assign a source based only on placement, color, or proximity to another number. If a proof surface names a metric but does not define it, use the named provider’s official definition for that metric and keep any TrustGrowth-specific interpretation separate.

Freshness must be read from a visible timestamp on the specific proof surface when one exists. A timestamp on one proof card or detail page should not be applied to another card, the entire proofs index, every underlying metric, or every upstream data source.

Read the date together with its visible label and location. A date may describe the state of the public proof, a measurement period, or another explicitly named event. If the surface does not define which event the date represents, report only the date and its displayed label. Do not turn it into an unsupported statement about when Search Console last collected data, when TrustGrowth last ran an audit, or when every score input changed.

Search Console has its own reporting timelines. Google notes that recent Performance report data can be preliminary and may change while it is still being collected. Google also explains that the report’s update date concerns the data available in that report. See Performance report: About the data for Google’s current freshness notes. That documentation defines Search Console reporting; it does not define a timestamp shown by TrustGrowth.

If no timestamp is visible on the specific proof surface, say that no visible timestamp is available there. Do not estimate freshness from the page’s position in the index, a browser cache date, a search-engine snippet, a copyright year, or the date of another public page. If a timestamp appears later, use the new visible state and identify the surface you read.

For screenshots or citations, preserve enough context to show the timestamp and the proof it belongs to. A cropped date without the card title or page identity can create ambiguity. Current-state reporting should make clear when the surface was observed, while keeping the displayed timestamp distinct from the observer’s access time.

They are different measurements produced under different systems. Search Console clicks and impressions describe search visibility and interaction according to Google’s reporting rules. A TrustGrowth score is a TrustGrowth evaluation. No one-to-one movement should be expected unless TrustGrowth publicly documents a specific rule for the score shown on that surface.

A TrustGrowth evaluation may reflect the current set of checks, findings, inputs, or scoring logic used by the product. Search Console performance metrics may cover a reporting window and can be affected by aggregation, privacy handling, result type, and data freshness. Because the definitions and update schedules differ, a score can move while clicks or impressions remain unchanged, and clicks or impressions can move while a score remains unchanged.

Do not infer cause from timing alone. If a score rises near the same time as impressions, the public proof does not by itself show that the score change caused the impression change. The reverse is also unsupported. The same caution applies to rankings, conversions, revenue, leads, and retention. A public snapshot can show values at a point in time without establishing why they changed.

For a defensible comparison, identify the exact proof surface, record its visible timestamp when present, name the TrustGrowth score, and compare Search Console metrics using the same metric definitions and reporting window. Google’s documentation on dimensions and data groupings explains why Search Console totals can differ when data is grouped by property, page, query, country, device, or search appearance.

If the visible proof does not expose the scoring formula or change history needed to explain a movement, say that the public surface does not provide enough information to attribute the change. That answer is more accurate than inventing a causal story.

A proof page does not prove future SEO gains, a future ranking for any query, increased traffic, improved conversion, revenue growth, or any other business outcome. It does not establish that a score caused a Search Console metric to move. It does not validate analytics or events that are not visibly named and sourced on the page. It does not show that Google endorses TrustGrowth or its evaluations.

It also does not make every nearby number comparable. Before comparing two values, confirm that they use the same definition, time window, aggregation level, and surface. Search Console can group data by property or page and applies metric-specific counting rules. TrustGrowth scores use TrustGrowth’s evaluation system. A numerical change in one system should not be restated as a percentage improvement in the other.

Treat absence carefully. If a metric, timestamp, explanation, or score component is not visible, the proof does not establish that it is zero, missing from the underlying system, or unchanged. It establishes only that the item is not visible on the surface being read. Similarly, a visible proof is not a complete audit trail unless the page explicitly presents one.

The safest public description names what is visible, names the provider of a defined metric, identifies the relevant timestamp when one exists, and states the limits. For Search Console concepts, link directly to Google’s definitions, including Getting started with Search Console and What are impressions, position, and clicks? For TrustGrowth-specific details, use only the definitions visible on the current TrustGrowth surface.

Read each proof as a bounded current-state record, not a promise or a causal result.