Home → Answers for fuel company websites → Who Should Control Search Console for My Fuel Company Website?

Who Should Control Search Console for My Fuel Company Website?

Your company should. Keep a verified owner on your own staff. Google requires at least one verified owner for people to keep access to a property. Google guidance

Reviewed October 18, 2026

Put access in the proposal

We suggest naming one responsible person at your company. Then give the provider only the access the agreed work needs. Write down who manages access and who handles a staff change.

A Search Console owner can add and remove users, change settings and view the property's data. Google guidance

During setup, ask the provider to show your role and theirs. Use one login per person, never a shared company password. Keep account recovery inside your own company process.

Match the permission to the job

For a first SEO audit, Google recommends giving the provider read access, not write access. Google guidance

Start the audit with the questions you want answered. After you review the findings, agree on which changes are approved and what access they need. A request to look at data is not permission to change your site.

Plan for the day a vendor leaves

Removing an owner does not remove their verification tokens. Remaining tokens can let that person verify again. Google guidance

Have the person who manages your accounts plan this review with care. Check what depends on a verification record before deleting it, and confirm your own access stays in place.

What should I check before accepting the handover?

Ask the provider for a written handover plan. As the dealer account owner, use this proposed acceptance checklist with the person who manages your accounts:

  1. Confirm your own access. Sign in with your own company-managed Google account, select the correct website property and confirm that you are a verified owner, not only a delegated owner. Check your verification method and that you can view the property's data. Google's owner and permission guidance explains where to check.
  2. List what remains. Review the provider's users and roles, ownership verification methods and any unused ownership tokens. Ask which website files, tags, DNS records or other services those methods depend on. Record the dependencies in your internal handover notes; do not share passwords or account recovery codes.
  3. Name the reviewer. Record who at your company will review any proposed user or token removals, who is authorized to carry them out and when your own access will be checked again. Keep unresolved dependencies on the handover list before accepting it as complete.

Ask the written plan to identify what stays, what is proposed for removal, the dependencies and the sequence for keeping your access working. A verification token may also support other Google services, so a removal needs a dependency review. This checklist is for your review, not an instruction to delete tokens or change DNS. It does not establish a provider's contractual duties or promise an ownership transfer.

Check website control-panel access, domain registrar/DNS authority and Search Console access separately. Page-editing access does not establish domain/DNS authority or verified Search Console ownership.

Keep editing and search access on the list

FuelSite.pro gives website customers control-panel access for edits. FuelSite.pro website services

That is a separate matter from Search Console. Request a demo and ask how Search Console access would be set up and who holds it when the project ends.

Request a Demo

Author: The FuelSitePro team