You open Google Search Console to check an important service page, but your website has disappeared from the account. Perhaps a developer has just rebuilt the site, the person who set it up has left, or your agency handover includes reports but no working access.
Start by identifying the account, the website property and the access you actually need. Then restore a verification method the business can maintain. Ask for evidence of each step, rather than accepting a screenshot from somebody else’s account as a completed handover.
Check whether access is lost or you are looking in the wrong place
Before asking anyone to change the website, record the Google account you are using, the property you expected to see and the exact message displayed. Check other business Google accounts you legitimately use. An empty property list and a failed verification message are different starting points.
A property is the website scope Search Console reports on. For websites, a Domain property covers the domain’s subdomains and protocols; a URL-prefix property covers the specified prefix. For example, https://www.example.co.uk/ and https://example.co.uk/ are different URL-prefix scopes. Google’s guide to adding website properties explains the distinction.
Compare the property with the address customers actually reach. If your old report used the non-www address and the current site uses www, note both. Do not commission tracking changes merely because two differently scoped reports show different figures.
For an agency handover, request the exact property name alongside the account email that should receive access. “We have added you to Google” is too vague to verify.
If an existing owner can help, use that route first
Ask the current owner to add your named Google account to the correct property. Google’s permissions guidance distinguishes verified owners, delegated owners, full users and restricted users. Only owners can grant access. Delegated ownership comes from another owner; verified ownership comes from proving control through a verification method.
Separate two needs in your request: access for everyday reporting and lasting business control. Someone preparing monthly SEO reports may need a different role from the person responsible for maintaining ownership.
Use individual accounts with a clear business contact responsible for each. Ask the recipient to sign in and confirm access themselves. Do not exchange a shared password to avoid setting up the appropriate role.
If the owner has left, restore verification
Google’s current ownership verification instructions say you can verify ownership yourself when the only verified owner has left. Verification is ongoing: Google checks that the verification token remains valid. Removing it can eventually cause access to expire.
Give your developer or domain administrator a focused request: identify the appropriate method, implement the record or file supplied for your account, and confirm successful verification from that account. Avoid changing several unrelated systems while investigating one access problem.
For a Domain property
Use DNS verification. Ask whoever maintains the domain’s active DNS to add the exact record supplied by Search Console. Google supports TXT and CNAME verification records. Keep the required record after verification succeeds.
Request an addition with a clear purpose, not a wholesale DNS replacement. The person making the change should identify where the live records are managed before editing anything. A domain invoice alone does not tell your developer which control panel currently serves the DNS.
For a URL-prefix property
Available methods include an HTML file or an HTML meta tag. For file verification, check that the supplied file is publicly reachable at the specified address. For tag verification, the tag belongs in the homepage’s HTML head. Follow the instructions for the method selected in your account.
If the website was recently rebuilt, ask the developer to compare the verification setup before and after launch. Check the method that was actually used rather than installing another plugin speculatively.
If verification still fails
Send the exact failure message, selected method, property name and change time to the person responsible. Ask them to confirm what Google can retrieve. Keep a short record of each attempted fix so the next person does not repeat the same unsuccessful change.
Do not remove the property as a reset
Deleting entries until something works makes a handover harder to follow. Google’s property removal guidance explains that removing a property affects access and notifications. If you are its last verified owner, other users lose access too. Where your valid verification token remains, adding the same property again and verifying can restore your access.
Before any removal, establish what problem it is supposed to solve, who still relies on the property and how access will be restored. Keep useful report exports and the handover record together.
If somebody suggests a new property, ask whether its scope matches the original. A newly added URL-prefix view is not evidence that access to the original Domain property has been recovered.
Will the old search data come back?
First try to recover the same property. Google’s property setup guidance says collection begins when someone adds the property, even before verification, and continues while a user retains it in their account. A genuinely new property may need a few days to show data.
Check the available date range and familiar pages once access returns. Do not promise that recreating a differently scoped property will reproduce every historical report. Compare like-for-like property names, filters and periods before deciding there is a data loss.
For example, ask for the same three-month report that appeared in the previous agency’s handover. If the results differ, record the report settings and investigate the discrepancy before using it to assess an SEO campaign.
Finish the former-owner handover carefully
Once your own verified access works, review former staff and supplier access. Removing a verified owner from the user list does not remove their verification tokens. Remaining tokens can let that person verify again. Check Unused ownership tokens and identify the relevant records.
Google also warns that a verification token can serve other products, including Merchant Center or Google Workspace. Have the responsible administrator check dependencies before removing it. Avoid deleting every Google verification record simply because one supplier has left.
Agree who will make each change and when. Ask for confirmation that the business retains working access afterwards. Include Search Console in the wider website handover instead of treating a single successful login as the end of the job.
What a completed recovery should include
Google’s property settings reference identifies Ownership verification, Users and permissions, and Associations as separate settings. Available controls depend on the property and your permissions. Check the selected property before assessing what is missing.
Ask your supplier to demonstrate these acceptance checks:
- Your intended business account can open the agreed website property.
- The recorded access level matches the person’s responsibility.
- The business knows who maintains the verification method.
- A familiar report can be opened and compared with an earlier export.
- Former-owner access and any remaining verification methods have an agreed resolution.
- The next website or domain handover includes a named person responsible for rechecking access.
Record the property, account email, method, responsible person and completion date in your business handover notes. You need a usable ownership record, not a folder of unexplained screenshots.
Make access part of the next website project
Put Search Console access on the acceptance checklist before a rebuild, supplier change or staff departure. Arrange the verification check while the outgoing and incoming people are both available, and repeat your business-account login after the work is complete.
If you need help untangling website ownership or turning recovered reports into a practical plan, explore our SEO services or contact BuzzBoost. Tell us the property you expect to access, the message you see and what changed recently, so we can identify the next useful step.
Featured image: AI-generated editorial artwork, not a photograph of a real BuzzBoost office, client or result.
