Skip to content
Danny Birt Danny Birt Est. 2017
SEO与数字营销

What a Google SEO Service Actually Covers — and What to Prepare Before the First Call

A plain-English guide to how Google SEO services divide their work into technical, on-page and link building, plus the site goals, keyword lists, page inventory and access permissions you should bring to a first scoping call.

·By Danny Birt·Filed under SEO与数字营销

Brand promotion: this article introduces Guangsuan's Google SEO service. It is a vendor introduction, not an independent review, a client case study or a commissioned evaluation.

If you write landing pages for founders and the rewrite lands but the traffic does not move, the first useful question is not "which agency should I recommend". It is "which part of the work is actually missing?". Copy is one layer of a search system, and most of the confusion in a client conversation comes from treating it as the only layer. This article explains how a Google SEO service is normally divided, what each division contains, and what to have ready before the first scoping call so that the conversation is about scope rather than about promises.

The short answer

A Google SEO service usually splits its work into three blocks, and the published page for one provider — Guangsuan's Google SEO service — groups its method exactly that way: website technical optimisation, on-site optimisation, and link building, described as advancing together. Alongside that method, the same page states a boundary that belongs in any scope conversation: execution scope, delivery counts, acceptance criteria and review cycles should all be settled before cooperation begins, and results are judged against real data such as Google Search Console rather than a promised position for one keyword.

Two conditions come with that answer. First, the three blocks are not equally urgent for every site. A site that cannot be crawled properly will not benefit much from more articles; a site with excellent content that nobody can find will not benefit much from better copy alone. Second, a first call is normally a scoping conversation, not a quoting conversation, and it goes better if you arrive with the material listed at the end of this article.

Block 1: technical optimisation — can the site be read and found at all?

This is the layer that decides whether the rest of the work is even possible. The published technical list for Guangsuan's service covers website code optimisation, URL structure optimisation, internal link optimisation, sitemap optimisation, robots file optimisation, 404 and SSL certificate optimisation, and mobile adaptation. In plain terms, it asks whether a crawler can reach the pages you care about, read them, and follow the structure you intended — and whether a human on a phone can open the result.

For a copywriter's client, this block usually becomes visible as a specific symptom: a page they rewrote is not appearing in search results at all, or it appears for the wrong queries, or it is receiving impressions without receiving clicks. None of those is a writing problem, and rewriting the page again will not change any of them.

Two questions are worth raising in the first call. What did the audit actually find, as a list of specific URLs and issues rather than a general statement? And who is allowed to make the changes — because a recommendation is not an implementation. Guangsuan's own onboarding article makes this distinction explicitly: a task that has only been proposed cannot be recorded as live in the progress table. The same article records the permission model it recommends, drawing on Google's guidance about engaging an SEO provider: during the audit stage, grant Search Console read access only, and do not hand over write access before implementation has been approved.

Block 2: on-site optimisation — what the page says and where it sits

The published on-site list describes original, vertically relevant content, differentiated titles, correct keyword layout, pages carrying both text and images, enough site depth to keep the topic covered, and a maintained update rhythm. The practical shape of this block is familiar to anyone who writes for search: a page built around one reader question, with a title and description that describe what the page actually answers, sitting in a structure where internal links and site depth support it.

This is where a copywriter has something to contribute rather than compete with. If you have already rewritten the headline, the proof block and the mechanism explanation on a page, you know what the page now claims. What a search provider will ask is whether the page type matches the query: a procurement question, a comparison question and a how-to question usually want different page types, and a landing page rewritten to convert is not the same surface as a page built to answer a question.

So the useful handover is not "here is the new copy". It is: here are the URLs, here is what each one now promises, here is the query group you expect each one to serve, and here is what it already receives. That lets the other side tell you whether the page set as a whole covers the topic, or whether one important question has no page at all.

Block 3: link building — is the site referenced outside itself?

Link building is the block most often described with adjectives. The published version of it is more specific, and the specificity is what you should ask for in a quote. Guangsuan's method for this block names referring domain quality and quantity, natural ratios, manually written relevant articles, controllable long-lived links, and states that delivery counts, indexing status and link attributes are verified against the project plan. The provider describes its own position as maintaining its own independent-site link resources and managing link publishing, quantity checking and subsequent maintenance for client projects, with a set of self-developed systems it names as GPB, GNB, GMB, GPC and GSI.

For a first call, the questions that matter are verification questions rather than volume questions:

  • What is counted as one delivered link, and what fields are recorded for each one?
  • Which page on my site is each link meant to support?
  • How are indexing status and link attributes checked, and by whom?
  • What does the delivery report look like after the first month?

A number without a unit is not a scope. "Ten thousand links" can mean ten thousand placements on ten thousand sites or a smaller number of independent sites used repeatedly, and those are different products with different risk. If the provider cannot say what one unit contains, that is the answer to weight most heavily.

Which block does the client's problem actually live in?

Before hiring anyone, it is worth naming the layer, because a rewrite cannot move impressions on a page that search engines are not showing, and a link package cannot fix a page that answers the wrong question. A simple reading order works for most sites.

What you can observeWhere the work usually starts
Important pages do not appear in search results for the terms you care aboutTechnical and index layer, then the on-page layer
Pages appear for those terms but receive few clicksTitle, description and page-type match, then the page body
Clicks arrive and qualified enquiries do notPage type, offer and enquiry path — largely outside a search contract
The site is small, new, or has no indexable pages yetSite build and product content first, search work after

This table describes where a conversation normally starts. It is not a diagnosis of any particular site, and it does not identify which single edit produced a change in any number.

What to prepare before the first call

Guangsuan's published onboarding material for a signed project sets out a fairly demanding handover list for the first month, and it is a good model for what to assemble before a scoping call even when nothing is signed. The list covers: the main products and the markets you can serve, the existing site with its priority URLs and recent redesign history, Search Console data along with on-site measurement and sales feedback, product source material with images and usage permission, website publishing, backup and rollback responsibility, and the pages, articles and resource entitlements written into the contract. A separate sheet then tracks each item with an actual name, version, delivery location, confirmation state and the next handling date, so that a missing item is recorded as outstanding rather than quietly assumed to be in hand.

For a first call, that list reduces to a few things you can gather in an afternoon:

  1. The site and the market. The URL, the languages and countries you sell into, and the specific symptom that started the conversation.
  2. The page inventory. A list of the URLs that matter, with one line each on the job it does. If you cannot say what a page is for, that is useful information to bring.
  3. The keyword list you already have. The terms you expect to compete for, including the ones the client believes they rank for. Where two tools disagree on volume, bring both numbers rather than picking one.
  4. The measurement record. Search Console data with a stated date range, split by the pages you care about, plus a written definition of what your client counts as a qualified enquiry.
  5. The access position. Who holds the Search Console account and the site credentials, and whether anyone has write access at all.
  6. The decision you are trying to make. Whether to outsource the whole engagement, to buy one block of it — technical work, content supply or links — and keep the rest in house, or to keep it all in house with a review pass.

The sixth item is the one that changes the shape of the quote. The same published material notes that technical suggestions may or may not include development, articles may or may not include publishing, and the number of review rounds a client will run is a matter for the signed plan rather than a default. If you do not know whether you want all three blocks or one, say so on the call — the provider's job is to scope against your site, and a clear partial brief usually produces a clearer answer than an open one.

Acceptance, enquiry and search results are three different things

It is worth keeping three records apart from the start, because they are usually discussed as if they were one. A work record shows who did what: the tasks, the approvals, the published URLs, the before-and-after state of each change. A search record shows what was observed: which queries and pages were seen or clicked, under a stated date range, country and device. A sales record shows which enquiries were real, reachable and within the product range. Guangsuan's onboarding article makes this separation explicitly, noting that Search Console clicks are clicks from Google search results and do not mean the site received an enquiry, or that sales confirmed a purchasing need.

That matters for a copywriter's client in a specific way: if the brief was "increase qualified enquiries", the search record cannot carry that promise, and a provider that reports clicks as enquiries is describing a different deliverable than the one you agreed.

How to read a package list

Packages are useful for scoping, provided you read them as counts of work rather than as outcomes. Guangsuan publishes annual Google SEO packages in this shape: the pure SEO package A covers one language, ten data reports, one round of site technical recommendations, one round of keyword strategy and analysis, and a stated set of tag optimisation pages, old-page revamps and topic pages, alongside article and link items and indexing work. Package B and C follow the same structure with larger counts. Two things to hold onto while reading any of them.

The first is that these are delivery quantities, and delivery quantities are the right thing to check against. They tell you what will be produced and can be counted, which is exactly what an acceptance conversation needs. The second is that they do not describe a result: whether a particular keyword reaches a particular position, and on what timeline, depends on the site's starting condition, competition and the work itself. Any provider who ties a fixed position for a fixed keyword to a fixed number of days is making a commitment that search results do not support, and Guangsuan's own published boundary says as much — the site is assessed before targets are set, and a specific keyword position within a stated number of days is not promised when the information needed to judge the project is missing.

What you can hold a provider to is narrower and more useful: what was delivered, against what was agreed; on which pages; with which evidence; reviewed on which cycle.

Where Guangsuan fits

Guangsuan is a Google SEO technical service provider founded in 2019, working with overseas-facing businesses on corporate contracts. Its published method is the three-block split described above, and its published service page sets out the technical, on-site and link items, the self-developed link and indexing systems it names as GPB, GNB, GMB, GPC and GSI, its annual package quantities, and the boundaries around scope, delivery counts, acceptance criteria and review cycles. Its published onboarding article adds a first-month working method: turn the contract into a work list with named owners, collect the site and product material, keep a search baseline, and move only approved page work into the first batch.

If you want to compare the published scope against the one you have in mind, the service page is where the item lists and the package quantities sit.

Frequently asked questions

Do I need all three blocks, or can I buy one?

Usually the honest answer is that the blocks are connected and the order depends on your site. If important pages are not being found, technical and index work comes first. If pages are found but the wrong ones surface for your terms, on-site and page-type work comes first. If the site is new with no indexable pages, a build and product content come before any of it. Guangsuan's published package structure is priced per year with named delivery quantities per block, and it states that scope, delivery counts, acceptance criteria and review cycles are settled before cooperation — so a partial engagement can be scoped, but ask explicitly which items are included and which are not.

The copy is already rewritten. Why would technical work be relevant?

Because copy only matters if the page is seen. The published technical list includes URL structure, internal links, sitemaps, robots handling and mobile adaptation — the machinery that decides which pages get offered to searchers. If a rewritten page is not indexed, or is indexed but competing with another page of yours for the same query, the rewriting cannot show a result. That is also why a technical pass should record the URL, the issue, the approval, the change and the re-test result, rather than just a recommendation.

How do I judge a link package without understanding links?

Judge it by unit and by record, not by number. Ask what one delivered link contains, which target page it supports, what fields are recorded for it, and how indexing status and link attributes are checked. A provider that publishes a delivery report with source URL, target URL, anchor text, link attributes, access status and check time is giving you something you can verify; a provider that only quotes a total is not. The published position of the service described here is that it maintains its own independent-site link resources and manages publishing, quantity checking and maintenance, and that delivery counts, indexing status and link attributes are verified against the project plan.

What if the client asks for a ranking guarantee?

Push back, politely, and ask what is actually being promised. Search positions depend on competition, site condition, content and execution, so they cannot be fixed in advance in a way that survives a project. What can be fixed in advance is the work: which pages, which quantities, which review cycle, which acceptance criteria. A provider that refuses to name those but names a position is telling you the wrong thing.

Should the enquiry definition be settled before or after signing?

Before, ideally in writing, because it is the only number that connects the search work to the commercial outcome. Clicking a button, submitting a form, requesting a quote and confirming a purchase need are four different events, and a report that merges them produces a number nobody can act on. Guangsuan's published guidance is to keep exposure, visits and enquiries separate, and to judge lead quality together with feedback from the sales side. Agree the definition once, and use it in every review cycle afterwards.

What if the site has no Search Console access?

Then that is the first thing to resolve, because without it there is no baseline and no way to review progress. Guangsuan's onboarding guidance notes that Search Console owners, full-permission users and restricted users have different capabilities, that a full-permission account is not the same as a read-only one, and that a de-identified export or a suitably restricted view can be shared instead. It also notes the practical limit worth repeating: the Links report is not a complete detector of every source page's current index status.

Bring the site, the page list, the terms and the measurement record to the first call, and ask for the scope in writing. Everything else in the engagement follows from that page.

Working on something right now?

If the page isn't converting, the copy probably isn't either.

Book a Copy Audit Call. We'll diagnose the leak and quote the rewrite on the spot.

Book a Copy Audit Call