UK firms often start the search for a Philippines SEO partner with a rate card. That is the wrong first document. Rate cards tell you what an hour costs. They do not tell you who owns google.co.uk performance, who writes British English, who can change robots.txt, or what happens when Search Console shows a collapse after a redesign. Scope those things before you talk about retainers, or you will buy activity and still have no owner for the ranking problem.
We work with UK companies from Quezon City. The useful part of that arrangement is not the timezone story. It is whether the brief forces the work onto the UK market, the UK site, and the UK buyer. A vague "do SEO" order produces generic English content, US SERP assumptions, and reports that look busy. A tight scope produces pages, links, and technical fixes that can actually compete in the United Kingdom.
Start With The Market, Not The Team Size
Write the market into the first page of the brief. Name google.co.uk as the primary search surface. Name the cities, nations, and languages you actually sell in. A firm that sells in England and Scotland is not the same brief as a firm that also needs Ireland. A company that only sells in London trades is not the same brief as a national ecommerce catalogue.
List the competitors you lose to, not the agencies you admire. Include the URLs that already rank for the money terms. A Philippines team that never sees those SERPs will write against an imaginary landscape. We need the live pages, the title patterns, the review volume, and the commercial offers. If you cannot name five competitors, you are not ready to outsource execution. You are still in strategy.
Spell out British English as a production rule, not a preference. Colour, organisation, tyre, metre, and enquiry are not cosmetic. They are ranking and trust signals on UK pages. The brief should say who edits for UK usage and who rejects US copy before it ships. If that editor is you, put the review window in writing. If that editor is us, give us a style sheet and examples of copy you would actually publish.
Lock Access Before You Lock Hours
SEO work without access is theatre. The scope should list every login the partner needs in week one, who grants it, and what they may change without a ticket.
Google Search Console must be at property level, not a PDF export. GA4 must be at the view you use for revenue, with conversion events named. The CMS needs an editor or developer role that can ship titles, canonicals, redirects, and schema. Hosting or CDN access matters when headers, staging noindex flags, or crawl delays sit outside WordPress. If your developers own those surfaces, name the internal owner and the SLA for implementing our tickets.
Be explicit about what the partner must not touch. Payment systems, customer data exports, and production deploys without a named approver belong on a deny list. UK firms that skip this either over-share or starve the campaign. Both fail.
Reporting cadence belongs in the same section. A monthly slide deck that restates rankings is not a control. We want a written list of what shipped, what moved in Search Console, what failed QA, and what is blocked on your side. Put the call in UK working hours. Manila overlap with the UK morning is usable if you book it. Do not assume Slack at midnight is a substitute for a decision.
Separate Diagnosis From Production
A lot of cheap retainers collapse diagnosis into "we will look at the site" and then start writing blogs. That is how you get 20 articles on a site whose category templates are noindexed.
The scope should buy a time-boxed diagnosis with named outputs. Technical crawl of the live UK host. Indexation review against Search Console. On-page sample of the commercial templates, not a random blog. Content map against the money queries. Link and digital PR baseline that names referring domains you already have, not a dream list. Then a prioritised backlog with effort, dependency, and expected evidence of success.
Only after that backlog exists should production hours start. If a vendor refuses to show you the diagnosis format before you sign, they are selling a package, not a campaign. Our SEO services for UK businesses are built that way: the UK SERP, the UK host, and the backlog come before content volume.
Name Deliverables That Can Be Inspected
Hours are not a deliverable. "Four blogs a month" is barely a deliverable. Write outputs you can open in a browser and reject.
For technical work: named URLs, the defect, the proposed change, the person who ships it, and the Search Console or crawl check that proves it. For on-page work: template or URL, title and H1 rules, internal links that must exist, and the snippet you want in the SERP. For content: brief, sources, UK English pass, publish URL, and the query the page is allowed to target. For links: target page, prospect type, and a rule that bans paid directory spam.
Put acceptance tests in the SOW. A blog that cannot rank because the category is canonicalised to a thin parent is not accepted work. A technical ticket that is "done" in a spreadsheet but still live-broken is not accepted work. If you do not write those tests, the vendor will mark tasks complete against their process, not against your revenue pages.
Volume caps belong here too. Unlimited content is a warning sign. So is a fixed article count with no keyword ownership. The brief should say which money pages may be created, which existing URLs must be improved first, and which topics are off limits because legal, compliance, or product cannot support them.
Decide Who Owns Risk During Change
UK sites get redesigned, replatformed, and moved to new agencies at the worst possible moment. The scope needs a change protocol.
If your developers ship a new theme, who checks robots.txt, noindex, canonicals, and the XML sitemap before go-live? If a staging clone is pushed to production, who confirms Google can still crawl CSS and JS? If URLs change, who owns the redirect map and the GSC inspection of the old money pages?
Write the answer. If the Philippines partner owns technical SEO, they need staging URLs and a freeze window. If your internal team owns deploys, the partner's job is a written go-live checklist and a 48-hour crawl after release. Leaving this as "we will coordinate" is how rankings vanish for six weeks while everyone argues about CMS tickets.
The same section should cover data protection. You are a UK firm. Say which personal data the partner will never receive. Say whether they work inside your tools or their own. Say how long reports and logins persist after the contract ends. None of that is glamorous. All of it is cheaper than a messy offboarding.
Ask Questions That Break The Sales Script
A discovery call that only covers price and "do you work with our CMS" will not protect you. Ask for a sample of a UK-market content brief they have actually used, with US spellings stripped. Ask how they treat google.co.uk versus google.com results in keyword tools. Ask who writes, who edits, and who is allowed to publish. Ask what they do when Search Console coverage shows "Excluded by noindex" after a launch.
Ask for the last time they refused a content idea because the page would not rank or would cannibalise a money URL. Vendors who never refuse are not strategists. Ask how they handle a client who wants 50 location pages for towns they do not serve. The honest answer is no, with a reason. The sales answer is yes, with a content calendar.
Ask what they need from you every month. If the list is empty, they plan to work in a vacuum. If the list is a novel, they plan to dump administration on your marketing manager. A workable UK-Philippines setup needs a named client owner, a 48-hour turnaround on approvals, and a developer contact for tickets that cannot be done in the CMS.
If you are comparing offshore models rather than a single vendor, read how we frame outsourcing SEO to the Philippines for UK businesses. The point of that model is senior work against UK demand, not a cheaper copy of a London agency's old deck.
Red Flags That Should Stop The Brief
Walk away from guaranteed page-one rankings. Walk away from a proposal that never names a UK competitor URL. Walk away from "native English writers" with no UK editor and no sample in British English. Walk away from link packages sold by volume. Walk away from a team that wants admin on Search Console but will not explain what they will change in the first 30 days.
Be careful with white-label chains. If the person on the call cannot name the people who will touch your site, you are buying a broker. We do white-label fulfilment for agencies, which is why we tell UK firms to ask who actually logs in. Direct clients should not sit behind a second reseller.
Price that is far below UK retainers is not automatically a trap, but it is a signal. If the quote only works by skipping diagnosis, skipping UK editing, or skipping technical QA, you will pay the difference in lost rankings. Ask what gets cut when the month is busy. If the answer is "nothing", they are lying. If the answer is "reporting design", that is survivable. If the answer is "technical monitoring", it is not.
What A Usable SOW Looks Like In Practice
A one-page SOW we can work from has six blocks. Market and language. Properties and access. Diagnosis outputs and date. Production backlog rules. Change and go-live protocol. Reporting, hours overlap, and exit.
Under market: United Kingdom, google.co.uk, British English, named competitors, named money URLs, excluded geographies. Under access: GSC, GA4, CMS, any tag manager, and the developer SLA. Under diagnosis: crawl, indexation, template sample, content map, link baseline, backlog. Under production: what may be created, what must be fixed first, acceptance tests. Under change: who checks robots, noindex, redirects, and sitemaps. Under reporting: monthly written record, UK-hours call, and the metrics that count as commercial movement rather than vanity.
That document is more valuable than a 40-page pitch. It also makes comparison fair. Two Philippines partners quoting different retainers are not comparable until both are bidding against the same SOW.
How We Prefer To Start
We start with the live UK site and Search Console, not a personality fit call. We want the money URLs, the current technical defects, and the content that already exists so we do not write over it. We will tell you if the first 90 days should be almost entirely technical and on-page, with little new publishing. That conversation is uncomfortable for firms that wanted a content calendar in week two. It is also how you avoid paying for articles that cannot be found.
If your internal team will keep publishing, we will scope our work as the technical and search layer, with rules for titles, internal links, and cannibalisation. If you want us to own content, we will scope briefs, UK editing, and a cap that matches what the site can support. Mixing those models without writing it down is how two teams ship two blogs for the same query.
UK firms that already have an agency and want a Philippines execution layer should say so. Dual ownership without a RACI is worse than no partner. Name who talks to developers, who talks to legal, and who can pause publishing.
When the brief is honest, a Philippines SEO partner is a capacity and cost decision, not a gamble. When the brief is a rate card, you are hiring hope. If you have a draft SOW and want it pressure-tested against a live UK site, send us the brief with the money URLs and the access you can grant in week one.
