The indexing handover a freelance website client can use
An illustrative handover that explains ownership, evidence and the next check.
Hand over decisions, not a mystery score
A freelancer launches a local business website and sends a screenshot marked SEO complete. The client still does not know who owns Search Console, where the sitemap lives or what to do if a service page is missing from search. This hypothetical example shows why a handover should transfer understanding as well as files.
Start with a short list of intended public pages. For each, record the final address and the job it performs. The home page, a service page and a contact page may all be eligible for search, while account or draft routes should have different treatment. Explaining that intent helps future editors recognise whether a warning represents a mistake.
Make ownership practical
The client should control the domain, hosting and relevant search properties through accounts they can maintain. Temporary contractor access is different from making the contractor the permanent owner of the evidence. Document where authorisation lives and how it can be revoked. Never include passwords or service secrets in a public handover file.
If IndexNow is installed, explain the key-file path and the publishing event that triggers submission. If Search Console is configured, show the correct property and sitemap location. A client should be able to repeat a basic check after the freelancer has left, without guessing which old dashboard contains the current site.
Deliver dated observations
Attach a report from the deployed site with a clear timestamp and scope. A sample of 20 pages is a sample, even if the entire site currently happens to be small. State whether JavaScript was rendered and which templates were inspected. If an audit could not fetch a page, record the error rather than silently treating the missing result as a pass.
For each unresolved item, describe the action and the evidence that would close it. For example, replace an accidental noindex directive, deploy, then confirm that the public response no longer contains it. Avoid promising a date on which Google will index the page. That outcome belongs to the search engine, not the handover contract.
Leave a manageable routine
Recommend checks after material changes such as a new publishing template, a domain move or a navigation restructure. The client does not need to inspect every unchanged page every morning. They need to know which changes can affect many pages and which tools answer the resulting questions.
Noor Indexer can produce an exportable technical sample for that handover. Its beta does not provide agency client accounts, shared private workspaces or ongoing monitoring. Present the JSON export as a dated evidence file, and combine it with a short explanation in the client’s own language. The best handover leaves the next person capable of acting.
Technical references
Primary documentation checked for this launch. Examples are illustrative unless explicitly described otherwise.
Continue reading
09An indexing routine for a small portfolio of websites
Keep separate sites comparable without pretending they share one search identity.
The small website owner’s field guide to indexing
A practical sequence from a published page to trustworthy indexing evidence.