By Touchbase Technologies · Published
An SEO agency proposal checklist for business owners
An SEO proposal should explain the work you are buying, who will approve it, how you will see the changes and how progress will be evaluated. A report containing more keywords or a promise to publish a fixed number of pages does not answer those questions by itself.
Use the checklist below to compare concrete assignments. It includes an original sample work ledger and a fictional comparison between two proposals. The examples are illustrations of a buying decision, not allegations about a real agency or evidence that one scope will produce a particular ranking.

State the assignment in terms you can verify
Begin with the business problem and the website pages involved. Perhaps customers cannot find clear information about a service, a site migration needs planning or useful public pages are difficult for search engines to access. Those are different assignments from writing articles or running paid advertising.
Ask the agency to separate diagnosis from implementation. A technical audit may identify problems, but its price does not necessarily include fixing them. A content brief may describe a page without including research, writing, original visuals, editing or publishing. Name those tasks explicitly.
Google's guidance on hiring an SEO recommends evaluating experience, communication and the explanation behind proposed changes. It also distinguishes paid advertising from organic search visibility. Treat those as useful checks on the proposal rather than accepting the phrase “SEO package” as a complete scope.
Before comparing prices, write down the audience, the relevant product or service, the pages you want to improve and the business action those pages should support. If you need help with customer research and outbound outreach as well, describe that separately; the customer-acquisition agency guide covers that broader assignment.
Ask for deliverables, inputs and evidence
A deliverable should leave something you can review. It might be an audit with reproducible findings, a redirect map, a revised page, an approved content brief or a report tied to dated source data. “Optimization” is a category of work, not enough detail to accept a result.
Use this suggested proposal-review sheet. It is a practical editorial framework, not a universal procurement standard.
| Proposal item | Question to ask | Evidence you should be able to review |
|---|---|---|
| Baseline | Which site property, pages and dates describe the starting point? | A dated report with its scope and source |
| Diagnosis | What is observed, and what is still a hypothesis? | Page URLs, examples and reproduction notes |
| Implementation | Who changes the site, and which changes need approval? | Named owner and a change record |
| Content | Who researches, writes, reviews and publishes each page? | A brief, source links and an approved final page |
| Dependencies | What access, materials or developer time must the client provide? | A list of inputs with owners and dates |
| Reporting | How will completed work and search observations be separated? | A work ledger plus dated search data |
| Ownership | Who controls accounts, files and materials after the engagement? | A clear handoff and access plan |
| Review | When will both sides decide what to continue or change? | A scheduled review and named decision-maker |
If the agency cannot answer yet, a paid discovery phase may be more honest than a detailed implementation promise based on a quick glance. Ask what that discovery phase will deliver and what decision it should enable. Do not assume it includes every later task.
Keep control of your business accounts
Ask which accounts the agency needs and why. Share access through the service's supported user-management system where possible rather than sending a shared password. Record the owner within your business who can grant, review and remove that access.
Search Console's permissions documentation distinguishes owners and users with different capabilities. Review the appropriate role for the work being done. A request for ownership deserves an explanation; it is not interchangeable with ordinary reporting access.
Also discuss the website platform, hosting, domain registration, analytics and any content assets. The agency may need a developer to implement a recommendation without needing ownership of the domain. Agree who retains the source files and how the next provider can understand the work if the relationship ends.
Do not change permissions you do not understand merely to speed up onboarding. Ask the person responsible for your systems to review access requests. This guide is a buying checklist; it is not an instruction to alter any live account.
Require a change ledger, not just a monthly slide deck
A useful work ledger connects the recommendation, the approved change and the verification. It helps distinguish an unfinished task from a completed implementation whose search outcome is still uncertain.
The following entries are fictional examples:
| Record | Before the work | Work delivered | Verification | Search outcome |
|---|---|---|---|---|
| Service page clarity | The page omits a confirmed service area | Owner approves the wording; editor publishes it | Live page contains the approved information | Monitor the relevant page and query evidence later |
| Redirect after a move | An old public link leads to a removed page | Developer implements the approved redirect | The old URL reaches the intended new page | Crawl and search observations may lag the change |
| New guide | A defined customer question is unanswered | Research, original example, editing and publication | Public HTML and links are checked | Indexing and ranking remain separate observations |
Include dates and actual page URLs in your real ledger. Keep a responsible person for each open task. If a recommendation cannot be implemented because the client has not supplied required material, record that dependency rather than showing the task as complete.
Separate publication, indexing, rankings and business results
These are different events. A page can be published and reachable without Google indexing it. An indexed page can appear for queries but receive no clicks. A clicked page may still fail to answer the visitor's question or produce a useful inquiry.
Google's technical requirements explain eligibility for indexing and explicitly state that meeting the requirements does not guarantee indexing. Ask reports to use separate labels for technical checks, Google's dated indexing observations and actual search-performance data.
For business results, decide what counts as an inquiry, a qualified opportunity or a sale before reporting them. State the source and time window. If call or in-person attribution is incomplete, show that uncertainty. Do not turn all branded searches, direct traffic or existing-customer purchases into proof that a new SEO activity caused the result.
This distinction also changes the review conversation. A public page that is blocked accidentally may need a technical fix. A technically accessible page that does not answer a distinct reader problem may need substantive editorial work. More pages are not automatically the answer to either problem.
Compare two proposals using the same reader problem
Imagine a fictional repair business whose service pages do not clearly describe the work it accepts. Proposal A offers eight articles each month. Proposal B offers a limited review of existing service pages, an implementation plan, two agreed page revisions and a dated work ledger. Neither proposal is automatically better. They address different work.
Ask Proposal A how the articles serve customer questions, how overlap with existing pages will be checked and who verifies technical claims about the repairs. Ask Proposal B what the review includes, who implements any technical changes and what happens if its diagnosis finds a different priority.
Then compare the assignments you actually need. If you do not have evidence that articles are the missing task, a page-count package alone is hard to justify. If your existing pages are usable but an important customer question is absent, a well-scoped article may be appropriate. The point is to make the decision from a problem and a deliverable, not the longest feature list.
Watch for promises that the provider cannot control
A proposal can commit to work, communication and review responsibilities. It should explain uncertainty around search outcomes rather than presenting a ranking position as a deliverable under the agency's control. Ask what evidence supports a forecast and what would make the team revise it.
Be cautious about a plan whose value depends entirely on a secret technique you cannot evaluate, a guaranteed top position or publishing material without the review your business needs. Request a plain-language explanation and examples of the proposed work. If the agency promises AI-search citations, ask which service, prompt, date and evidence would establish that observation instead of accepting a vague visibility score.
Do not confuse a refusal to guarantee a search outcome with a refusal to be accountable. An agency can still be accountable for whether it delivered the agreed research, implemented an approved change correctly and reported accurately.
Make the first review a decision point
Before work begins, agree when you will review implementation progress, dependencies and available evidence. For a small assignment, a first review might focus on whether the baseline was captured, the important findings were explained and the initial changes were approved or delivered. This is an example review structure, not a promise that search results will change within that interval.
Keep the resulting decision short: continue the current scope, change a priority, wait for a dependency or stop the work. Assign one owner and a next review date. The marketing-calendar guide shows how to put preparation and review work beside publication dates rather than treating the calendar as a posting quota.
If you are also evaluating Touchbase for your own acquisition workflow, review its current plans and allowances separately. A software account and an agency engagement are different purchases; neither removes your responsibility to approve accurate information about your business.
Questions before choosing an SEO agency
Is a proposal with more articles always better?
No. Ask which reader questions the articles answer, how they differ from existing pages and who checks their accuracy. A smaller assignment may be more useful when the problem is an existing page, an implementation dependency or a missing approval process.
What should I receive in a monthly report?
Ask for a record of completed and open work, the pages affected, important dependencies and dated search observations with their sources. Keep the interpretation and next decision visible. A traffic chart without the underlying work record leaves important questions unanswered.
Can the agency guarantee that every new page will be indexed?
Google controls indexing. Ask the agency to verify public accessibility and discovery, record actual Search Console evidence and explain exclusions it can diagnose. An indexing request or sitemap acknowledgement is not the same as an indexed-page confirmation.
Editorial context
A small-business discussion about evaluating SEO services helped identify the reader question. The technical references in this guide are Google's documentation. The example proposals are fictional, and this guide does not evaluate the individual dispute described in that discussion.
Prepared with AI assistance and checked against the sources linked in this guide.
Your next step
Get started with Touchbase
Find relevant customers, prepare outreach for review and keep contacts, replies and follow-up connected.
Start for freeStart with a Free account. Upgrade or add credits when you need more capacity. Compare plans