The direct answer

Set up Search Console with verified ownership of the correct site, then submit the canonical sitemap and record an initial baseline. A Domain property can cover protocol and subdomain variants through DNS verification.

Choose the ownership boundary

Use an agency-controlled Google account and decide who remains the accountable owner when vendors change. A Domain property is useful for a domain-wide view because it covers protocol and subdomain variants. A URL-prefix property represents a particular prefix instead. Google requires DNS verification for a Domain property; choose the property deliberately rather than selecting the first convenient option.

Keep a setup record with the property name, primary owner, DNS administrator and sitemap address. Give collaborators the access their tasks require. Avoid making a departing contractor the only person capable of restoring verification.

Verify through the actual DNS provider

In Search Console, add the property and copy the verification record exactly. Find the provider serving authoritative DNS for the domain. The company that sold the domain and the company serving DNS may differ. For a Cloudflare-managed domain, check the correct zone before adding the supplied record through its DNS interface.

Google's instructions explain that verification records must remain available after setup. Save the record purpose alongside it so a later DNS cleanup does not remove it. If verification fails, compare the live record with the supplied value before repeatedly creating new tokens.

Inspect the site that searchers will use

Open the homepage, a service page and an article on the public domain. Confirm that they load at the intended HTTPS addresses and that accidental staging links are absent. Submit the live sitemap through Search Console. Then use URL Inspection to examine a representative page and compare its reported state with the intended canonical URL.

These checks answer different questions. Ownership confirmation proves access to the property. Sitemap submission supplies discovery information. URL Inspection helps examine an individual URL. None of those actions establishes that a brand-new page will earn a particular query position or produce an inquiry.

Create a baseline that can be interpreted

Save the launch date and the initial list of public pages. As data appears, review queries and landing pages separately for branded agency searches, local service searches and marketing questions. A marketing-services site should flag beneficiary searches as an audience mismatch when evaluating commercial usefulness.

  • Record impressions and clicks with their date range and filters.
  • Compare a page's actual query themes with its intended reader decision.
  • Add qualified inquiry counts from the intake system as a separate business measure.

Use a realistic first-week example

Imagine a new site publishes fifty guides and Search Console initially shows only a few discovered URLs. First confirm sitemap accessibility and internal links. Inspect one missing guide for accidental noindex or an incorrect canonical. Correct the specific cause and record it. Publishing another fifty pages before understanding the first group adds uncertainty to the experiment.

Schedule a weekly editorial review alongside daily technical monitoring. Daily checks are useful for outages, access loss and serious errors; content decisions usually need enough observations to distinguish a real pattern from sparse early data. Keep changes small enough that the next review can explain what happened.

Questions agents ask

Can verification be done before traffic exists?

Yes. Ownership setup can precede meaningful traffic; performance data accumulates according to Google’s reporting and actual search activity.

Sources & further reading

Primary references for the rules and platform mechanics discussed here. Templates and recommendations are Medicare Marketing’s planning guidance. Examples are illustrative unless explicitly sourced.

Turn the idea into a next step.

Use the free toolkit to check your local foundation, build a content rhythm, or plan a webinar.

Explore the tools →

Keep reading