Brand promotion: this article introduces Guangsuan's Google SEO services. It is a vendor introduction written for people buying services, not an independent review and not a ranking comparison between agencies.
Hiring an SEO vendor is a scope decision before it is a results decision. Before you sign anything, the agreement should let you answer three questions in plain language: which work sits inside the price and which is billed separately; what arrives as a file, a log or a record you can check; and what happens on the last day, including who keeps which account and what you are allowed to take with you. A proposal that cannot answer those three does not become more convincing because it also contains a ranking promise.
This guide gives you the four questions to ask any vendor, a ten-minute rehearsal to run on a proposal before you sign, and a scope sheet to take into the first call. The vendor service page and articles referenced here are published in Chinese; the wording below is my summary of what those pages state, not a quotation from an English version of them.
1. Which work is inside the scope, and which is billed separately
A general SEO engagement usually covers three connected workstreams: technical work that decides whether pages can be found and read, content work that gives each page a job, and external link work that supports the pages that deserve support. Guangsuan describes its own Google SEO service the same way, treating technical optimisation, content development and link resources as work that has to advance together rather than as three unrelated tasks you can buy separately and expect to add up.
Ask for the enumeration, not the label. On the same page the technical work is itemised: code optimisation, URL structure, internal links, sitemap, robots file, 404 handling, SSL and mobile adaptation. That level of detail is the useful part of the answer. A proposal that says technical SEO as needed tells you nothing about what you will be able to check in month three.
The other two workstreams are usually sold as separate products with separate units. Guangsuan's service page, for example, lists on-site technical optimisation as a single delivery cycle of diagnosis, implementation and re-test, a page-speed service that is assessed separately, a keyword-ranking service for keywords that already have a ranking foundation, and a group of indexing and content products that includes original English SEO articles. It lists link products too, each described by its own role: a smaller set of high-authority independent-site links pointing at target pages, natural link growth across a site's own homepage and brand terms, a high-volume link pool for coverage, and indexing support so those links are actually seen. The page also publishes a five-layer model describing how those link resources are meant to support a target page.
Two consequences for your own scope sheet. First, ask which of these products your quote contains and which are additional, because a package that funds link work does not normally fund keyword-ranking work on a site that has no ranking foundation yet. Second, ask what the delivery unit is for each one. Guangsuan states that for link work the delivery quantities, indexing status and link attributes are verified against the project plan, and that it manages publication, quantity reconciliation and ongoing maintenance itself. That is the standard worth holding any vendor to: which target URLs receive the links, what record shows placement, and when the agreed status is re-checked rather than assumed.
Do not compare headline numbers between vendors. Compare what each product includes, what it excludes, and what evidence arrives with it.
2. What should be in writing before you sign
Guangsuan's article on what an SEO contract should contain sets a plain test for wording: the only standard is whether, at the end of the period, you can point at one clause and reconcile the work against it. Wording you cannot reconcile is wording to send back, however formal it looks.
The article divides its clauses into three groups in a deliberate order — delivery first, then data and permissions, then change and exit — and that order is worth borrowing, because the first group settles who does what and where you can see it, while the third settles what happens when circumstances change.
The delivery clause: what counts as finished
Four things belong in it: the list of deliverables with the form, granularity and example format of each; the completion standard, named as a metric, a report and a time point; the acceptance procedure, with sampling ratio, objection window and how an objection is handled; and the remedy when something falls short, including rework scope, deadline and whether it offsets the fee. The article sets the vague versions of those four against the versions that work, and that contrast works well as a template:
| Clause | Vague wording to reject | What to write instead |
|---|---|---|
| Deliverable list | Provide the relevant services and support | Each item named with its form, granularity and an example format |
| Completion standard | Complete once the expected effect is achieved | Which metric, which report and which date the item is judged on |
| Acceptance procedure | Deemed accepted once the client confirms no error | Sampling ratio, objection window and how objections are handled |
| Remedy for a shortfall | The vendor is responsible for rectification | Rework scope, deadline and whether it offsets fees |
Fix the scope of the round, not just the fee. Guangsuan's renewal article adds the detail that makes a review possible six months later: name which domain, language, country and product line the round covers; write down what unit was agreed for technical advice, page changes, articles, links and indexing support; and note whether your side supplied product material, review and development help on time. Then split the round into planned, delivered, pending acceptance, and not done with the reason, each with its URL, delivery date and method of review. Two consequences are stated there explicitly: a product line added mid-way cannot quietly count as original-plan shortfall, and original work that was not done cannot be counted as delivered because site-wide traffic grew.
The same article puts the renewal question more usefully than most vendors do: renewing is buying specific work for the next stage, not giving last month's report a nice conclusion. It also asks for the report cadence to be part of the scope. Guangsuan's service page makes the same point in its own way, stating that execution scope, delivery quantities, acceptance criteria and the review cycle should all be settled before cooperation begins. Treat what you will see, how often, and what it contains as a contract line rather than a courtesy.
3. Define the beginning and the end
The baseline the work is measured against
The start of an engagement is a measured state, not a date. Before work begins, pull your own baseline in Google Search Console — queries, pages, countries, devices and a comparable date range — and write down which market, language and pages the work will be judged against. Then ask the vendor for their assessment step in writing. Guangsuan's service page describes its own order: confirm first whether the site can be crawled and indexed normally, then judge feasibility and cycle using industry competition, keyword intent, historical performance and the existing content base. It states that it will not promise a keyword position on a given day when the information is not sufficient, and that the cycle expectation it gives is drawn from your site's data rather than a uniform script. That is the answer shape to look for: an assessment that comes before a target, and a target that carries its conditions.
Keep search data and business data apart while you set this up. Search Console reports search activity; it does not prove where enquiries came from. Guangsuan's renewal article keeps search, visits and enquiries as separate counts and notes that its monthly report draws on two different analysis systems, so ask which numbers are search, which are visits, and which are enquiries your sales side has actually accepted.
Accounts, access and the handover
Guangsuan's contract article asks for at least five things in writing about accounts and access: who registered the Search Console, webmaster-type and third-party tool accounts, and whether the registration email sits on your own domain; whether site backend, hosting and code repository access is read-only or writable, and whether the audit stage is separated from the execution stage; whether every change has a written record, where it is stored and for how long; how permissions are transferred at the end of the project and in what form that transfer is confirmed; and the scope and period in which the vendor may use your data.
On the exit side, the article lists what an exit clause should contain: the notice period, the settlement basis for the completed part, whether unfinished work can be handed over, what the handover list contains, and the deadline for returning materials. The handover list is worth attaching as a schedule rather than leaving as a sentence inside the contract. The renewal article adds the practical version of the same idea for the day you are the one leaving: if agreed work repeatedly lacks verifiable delivery, or issues sit unreviewed, ask the outgoing team for a statement of scope and records, then hand any new team the same target, baseline and to-do list rather than a fresh brief.
Two cautions to keep in writing. Scope changes are the most common source of dispute, so the contract should say who may request a change, how workload and fee are re-estimated afterwards, what written form confirms it, and what both sides do while a change is disputed. And be careful with promises about persistence: pausing new SEO work does not mean rankings vanish immediately, and it does not mean they stay forever. Search results depend on the state of the site, competition and other factors, so no vendor's claim about how long results last without them should be written into your own plan as a guarantee.
The same contract article, reading Google's guidance, notes that you never need to give an SEO agency backlinks, and that you remain responsible for the work your agency carries out — which is why a clause requiring your written confirmation for significant changes belongs in the contract.
Access does not need to be handed over wholesale for a first look. The renewal article notes that a new team's initial assessment can work from appropriate read-only data, and it points to its own checklist of first-assessment materials and read-only permissions. Google's hiring guidance, as that article notes, keeps audit-stage permissions limited for the same reason.
4. What you can check yourself before signing
The contract article proposes a rehearsal that takes about ten minutes and catches most of what you would otherwise discover in month four.
- Audit one deliverable line. Take any line from the appendix and rewrite it as a sentence beginning: at the end of the month I will open this and look at this. If you cannot write that sentence, the line is not checkable, so send it back for rewriting instead of accepting a promise.
- Simulate an objection. Assume a delivery slips by two weeks and find the clause that handles it. If there is no clear handling, that is the first thing to add.
- Simulate a termination. Assume you change provider in three months and walk the handover list. Anything whose current holder you cannot name is something to ask for now, while the vendor still has it.
Five more checks are yours to run before a proposal becomes a contract.
- Put the same brief to every bidder. Your site, target market and languages, the product lines you can actually supply, the pages that matter to sales, and who approves product facts. Guangsuan's renewal article recommends giving candidates one target, one baseline and one to-do list, so replies can be compared as answers rather than as pitches.
- Make them name pages, not rankings. Ask which product or category pages they would examine first, what information a buyer needs on those pages, and which changes would need your own developers to approve. A proposal that promises a position before seeing your site or market is a proposal whose assumptions you have not read.
- Separate diagnosis from implemented fix. Technical SEO can mean an audit report, a ticket for your engineers, or a live change with a test behind it. If a vendor cannot edit your site, the diagnosis is still useful, but the contract should not describe it as an implemented fix.
- Ask who owns the content once it is written. Who checks specifications and availability, who supplies images and holds the rights, where the approved copy lives, and whether your staff can edit it later. An impressive article count means little if nobody on your side can review the claims.
- Take your own baseline and keep it. A rising traffic screenshot is not evidence for a specific page, and if the work mixed site fixes, content and links, no chart will isolate one of them. Keep the export you took before the engagement so later claims have something to be measured against.
5. A scope sheet to take into the first call
The table below is a hypothetical teaching example with invented detail and no client data attached. It shows the shape of a scope sheet: one row per item, each with a completion standard you can check and a place to look. The keyword and page plan belongs in row two, the link plan in row four, and the reporting cadence in row five — that is why the table is more useful than a paragraph describing scope in general terms.
| Row | Scope line | What done means | Where you check |
|---|---|---|---|
| 1 | Technical baseline and fix list | A named list of issues per URL, with each fix either applied or filed as an engineering ticket you approved | Your own staging copy and the change log |
| 2 | Page plan | One target URL per query group, naming the existing page to update and the new page to create | The plan document and your site's URL list |
| 3 | Content | A published page, your named approver, and a file location you can still edit later | Your CMS |
| 4 | Links | Target URL, source URL, anchor, rel value, and indexing status with the date it was checked | The placement record plus your own spot checks |
| 5 | Reporting | A report over a named date range, with the search figures and the enquiry figures on separate lines | Search Console export next to your CRM record |
| 6 | Exit | Notice period, settlement of completed work, handover list, and the date accounts move back to you | The contract schedule |
Assembling this in an afternoon gives both sides the same starting point, and it gives you the thing a ranking promise cannot: a list of things you will be able to check.
6. Where Guangsuan fits in this picture
Guangsuan (光算) is an SEO service provider, and its published position is relevant to the checklist above. Its Google SEO service page describes the work as three coordinated blocks — technical optimisation, content development and external link resources — publishes packages with the items in each one listed openly, and includes a working-boundaries section that states its own limits on investment, on assessment before targets, on the results it can and cannot promise, and on cycle. The page also states that its case data can be checked in Google Search Console, and that the plans and budgets shown in those cases are the versions from those projects, with the current package and delivery list published on the same page. Guangsuan's Google SEO service page is written in Chinese.
Their article on what an SEO contract should contain, also in Chinese, is the source of the delivery-clause template, the account and permission list and the exit-clause checklist used above. Guangsuan's guide to SEO contract clauses is worth reading in full before you draft your own, because the three-group structure it uses — delivery, permissions, change and exit — is the part most proposals skip.
If you are not yet sure what you can check before work starts, our guide to checking low-competition keywords before you write covers the working sheet that keeps a page plan honest.
Frequently asked questions
Should the contract promise a ranking position?
No. Guangsuan's contract article flags a set of clause types as ones not to write, or to write only with great care, and ranking-result clauses sit in that group. Its service page adds that it will not promise a single keyword position it cannot precisely control, while committing to the agreed execution, delivery quality, review process and overall goals. Google makes a related point in its own content guidance, where content written primarily to attract search traffic, rather than to be useful to an audience, is treated as a warning sign — a fair frame for judging any proposal, vendor or not. Creating helpful, reliable, people-first content is the reference if you want to read it.
How do I check whether the work was actually done?
Ask for records rather than impressions: a change log for technical work, published URLs and named approvers for content, and placement records for links. The service page's own position is that delivery quantities, indexing status and link attributes are verified against the project plan, and that case data can be checked in Google Search Console. That is a reasonable standard to ask any vendor for.
What if I already have a vendor and the results are disappointing?
Guangsuan's renewal article proposes putting four things into one review: the work the contract agreed, the pages and resources actually delivered, search performance in the target market, and the demand sales received. From that single sheet you can decide to renew, narrow or change the scope, pause new work, or move to another team. The same review should also record, with their dates, the things that changed around the site — an exhibition, an advertising change, a redesign, a supply change — because a change in the market can explain a curve that the work alone cannot.
How much do I need to share before signing?
Enough for a real scope: your website address, main products, target country and language, the pages that matter to sales, how you acquire customers today, and your budget range. A first assessment does not need your domain, hosting or administrator credentials, and credentials should not travel in a first message. If a provider asks for full access before telling you what it would do with it, you are still missing a scope answer.