Imagine a business owner in Beaumont finishing a new website. The photos are in, the phone number works, and the services finally make sense. Then comes the obvious question: how do I know what Google can see? I would start with Google Search Console, because it gives that question somewhere useful to go.
Start with ownership, before the code
My first question would be who should control the property when this project is finished. The answer should be clear before anyone starts changing a website. The owner needs a durable way to see the reports and invite help. A launch should leave the business better informed, not dependent on a screenshot someone occasionally sends.
For this guide, I use example.com and an obvious placeholder. Neither belongs in a real verification attempt. Keep the working values inside the actual setup process; an educational article does not need a business's verification details.
Choose what you want to measure
In Search Console, open the property selector and choose Add property. For a website, the important choice is Domain or URL-prefix. A Domain property such as example.com includes its subdomains and protocols. A URL-prefix property such as https://example.com/ covers that exact prefix; http:// and https://www. are different scopes. Adding a property enables reporting; it does not improve the site's position in Search. Google explains property types and their coverage.
I would choose this deliberately. If the question is how the whole domain performs, use a view that covers the whole domain. If the question concerns a particular website address or section, a narrower view can be useful. A quiet report is difficult to interpret when it is looking at the wrong version of the site.
The Domain route uses DNS
Domain-property verification uses a DNS record. Follow the verification screen's record instructions through the person authorized to manage the domain, then return to Search Console to verify. A homepage HTML tag is not a substitute for Domain verification. DNS changes may need time to become visible. Google's ownership verification instructions cover the available methods.
As a working habit, I would write down the selected property and the person responsible for it. That small handoff note is useful months later, when the business changes a website or brings in another professional. It also makes the difference between domain ownership and page editing easier to understand.
The HTML tag route belongs in the head
For an eligible URL-prefix property, select HTML tag verification. Copy Google's supplied tag into the homepage's <head>, before the <body>. The visible header, navigation, and article body are different parts of the page. This demonstration shows only the placement:
<head>
<meta name="google-site-verification"
content="YOUR_SEARCH_CONSOLE_VALUE">
</head>Publish the change, then use Verify in Search Console. Leave the valid verification method in place afterward: Google can recheck it. See Google's HTML tag verification requirements.
Check the page Google actually reaches
For tag-based verification, Google checks the page reached by a visitor who is not signed in, including the destination of a redirect from the property's URL. Check that public destination's source for the tag, rather than relying on an unpublished editor preview. Google documents redirects and verification checks.
My troubleshooting order would be simple: confirm the selected property, open its public address, check where it ends up, and inspect the published source. Change one thing at a time. Otherwise, a correct setting can get replaced while the original problem is still waiting somewhere else.
Give the business a clean handoff
Owners can manage access in Settings → Users and permissions. Google distinguishes owners, full users, and restricted users. Assign the access needed for the work and review who retains it when the engagement ends. Removing a verified owner can also require removing their verification token. Google details permissions and ownership management.
I would include a plain-language note saying what was verified, who owns it, and where the business can find its reports. The owner should be able to explain the setup without memorizing a line of HTML. That is one reason a qualified professional is valuable: the work includes continuity and understanding, not just getting a green confirmation message.
Verification opens the door to better questions
Next, inspect an important page. URL Inspection distinguishes information about Google's indexed version from a live test of the current URL. A successful live test does not guarantee the page will appear in search results. Google explains what URL Inspection can establish.
For a local website, I would begin with the homepage and the page that explains the main service. Keep a short record of the date and what was checked. The first useful milestone is knowing where the evidence lives. From there, sitemap checks, indexing questions, and performance reviews become a process the owner can follow.