Brand promotion: this article introduces Guangsuan's Google indexing service (GSI). It is a vendor introduction, not an independent review or a commissioned evaluation.
SaaS teams meet the same message in Search Console: a product page, a documentation page or a launch post sits under “Discovered – currently not indexed” for weeks. The page loads, the copy is finished, and it still does not show up for its own title. That is usually the moment paid indexing help starts to look attractive.
This article answers one question for that team: what does a Google indexing service actually do, and what should you check and prepare before you ask for one? The status definitions below follow Google's page indexing documentation, and the service description follows Guangsuan's published GSI page. Nothing here is a promise about your own indexing or rankings.
The short answer
A Google indexing service works on the first two steps of a three-step chain: letting Google know that a URL exists, and increasing the chance that Googlebot fetches it. It does not decide whether the page enters the index, and it does not produce rankings. Guangsuan states that boundary on its own service page: the technical work addresses the opportunity to be discovered and crawled, while whether a page is indexed, when, and whether it stays indexed is decided by Google.
Three conditions belong with that answer:
- A new page or site can take about a week before Google begins crawling and indexing it, so a quiet first week is not by itself a fault.
- The service is relevant when the URL is reachable and indexable. A page blocked in robots.txt, marked
noindex, redirecting elsewhere, or duplicating another page is a site-side fix first. - If Search Console reports that the page was already crawled, the open question is about the page and its canonical, not about sending more crawl requests.
What the status actually tells you
Google defines the label narrowly: “Discovered – currently not indexed” means the page was found by Google but has not been crawled yet. “Crawled – currently not indexed” describes a later point in the same process: Google fetched the page but did not add it to the index. Guangsuan's own explanation of the discovered status notes that Google often attributes it to a deferred crawl, which is why the last crawl date can be empty on the report.
| Status in Search Console | What is confirmed | Where to look first |
|---|---|---|
| Discovered – currently not indexed | Google knows the address; the current record has no crawl yet | Internal links pointing at the URL, its sitemap entry, server availability |
| Crawled – currently not indexed | The page was fetched but did not enter the index | The fetched version, duplicated or near-duplicate pages, canonical choice |
| Page with redirect | The address you submitted is not the final destination | The redirect target, instead of repeatedly resubmitting the old address |
Neither label is a verdict. The crawled state does not by itself prove that the content is poor, and the discovered state does not by itself prove that your server is overloaded. Google's guidance is also that it is fine for a URL not to be indexed for a good reason — an intended robots.txt rule, a noindex tag, a duplicate URL, or a page that was removed and has no replacement — and that only the canonical version of each important page needs to be in the index, not every URL on the site.
Checks worth completing before you pay for indexing help
Several reasons a page stays out of the index belong to the site rather than to Google. Run these checks on the specific URLs you care about, not on the domain as a whole.
- robots.txt. Google lists a robots.txt rule that blocks Google from crawling large sections of a site among the reasons large groups of URLs are not indexed. Test the exact path and user agent, not just the file.
noindex. A noindex directive keeps a reachable page out of the index, and a leftover from a staging or preview setup is one way this happens. Check robots.txt and noindex separately rather than stopping at the first one that looks allowed.- Duplicates and canonical. If several URLs serve the same or very similar content, Google may index one version and treat the others as alternates. That can be intended behaviour rather than something to fight.
- Response code and redirect path. Record the original URL, every hop and the final page, so you compare the version Google would actually see.
- Discovery path. Google can learn about an address from a link on a page it already knows, or from a sitemap. No number of internal links guarantees indexing, so check whether the URL is reachable at all — a page that exists only in the sitemap is easy to miss.
- Recent changes. Write down when the page was published, when any block was removed and when the content last changed. If the last crawl predates the fix, the report may simply be describing the older version.
One expectation is worth setting here. Google notes that it recrawls pages automatically, so repeating a recrawl request for an unchanged URL is not the fix. Use a recrawl request sparingly, for a small number of important pages that genuinely changed.
What Guangsuan's GSI service covers
Guangsuan describes GSI, short for Google Speed Indexing, as its own indexing-promotion service name. Its page states that GSI is not a Google product, an official partnership or a priority-indexing permission. The work is described as crawl discovery and indexing promotion around the URLs you submit, carried out through Guangsuan's self-built GPC crawler pool and related link structures.
The published process has three stages.
- Confirm the URL is suitable to submit. The page should be reachable and free of obvious crawl blocks,
noindexdirectives, redirects or duplicate-canonical problems. Submitting a blocked page does not help. - Promote discovery and crawling around the target pages. Pages that can be discussed include a homepage, topic pages, product pages, article pages, and external pages you are authorised to operate.
- Verify at an agreed time. The service separates “submitted”, “crawled” and “indexed”. Scope, observation period, verification method and reporting are confirmed before cooperation, and where you have access to the property Guangsuan points to Search Console's URL inspection and Page indexing report. For a third-party page without Search Console access, the available verification route is confirmed in advance.
The service is scoped by URL batch rather than by seat or by month, so the list of pages you bring matters more than the size of the site. Two published qualifiers are worth reading before any budget conversation: the reference indexing-rate range of 60%–90% is stated as a reference interval rather than a guarantee for any batch of URLs, and the published time windows are service references affected by page quality, site status and Google's processing rather than a fixed deadline.
What it does not promise
- A guaranteed place in the index. Whether a page is indexed, when, and whether it stays indexed is Google's decision. Submission is not indexing, and indexing is not ranking.
- A ranking. Indexing makes a page eligible to appear in search results. It does not give the page a position, and an indexed page is not guaranteed to appear for every relevant query.
- A permanent index entry. A URL can leave the index later because of content quality, duplicate pages, canonical changes, access status or Google's own judgement.
- A repair for the page. Crawl guidance and any related link operations should comply with Google's spam policies, and the service cannot bypass Google's quality judgement or replace content and technical fixes.
What to prepare before the first conversation
A short, factual list keeps the conversation about your pages rather than about a package size.
- The exact URLs you want fetched — product, documentation, pricing or article pages — written as final addresses rather than as redirect sources.
- The current status of each URL, as Search Console reports it today, with the date you looked: indexed, discovered but not crawled, or crawled but not indexed.
- Reachability evidence. Confirmation that each page loads for someone who is not signed in, with no login wall, no 404 and no mistaken
noindex, and that its canonical points at itself or at the intended version. - Page type and priority. Which of these pages carry commercial value, so the list can be ordered instead of dumping the whole sitemap.
- A baseline. Impressions and clicks for those pages over a named date range, so both sides compare the same numbers later.
- A small sample. Guangsuan suggests bringing three to five example URLs with Search Console screenshots, the check date, the sitemap address and whether a redacted server log can be provided.
- Your verification plan. Which tool you will use, at which checkpoints, and who records the result.
Where Guangsuan fits
Guangsuan's GSI service is aimed at URLs that are reachable and indexable but are not being crawled or indexed, and it is checked through observable records rather than through a promise about your search results. If you want to see how the scope, the batch sizing and the verification terms are described before you send anything, the Guangsuan GSI indexing service page sets them out, and Guangsuan's walkthrough of the discovered-versus-crawled diagnosis is a reasonable next read if you are still deciding whether your case is a crawl problem or a page problem.
FAQ
Is a Google indexing service an official Google product?
No. Guangsuan states that GSI (Google Speed Indexing) is its own service name, built on technical operations that include its GPC crawler pool, and that it does not represent a Google product, an official partnership or a priority-indexing permission.
My SaaS page says “Discovered – currently not indexed”. Is that where the service helps?
That is the direction the work addresses, provided the URL is reachable and free of an obvious crawl block, a noindex directive or a duplicate-canonical problem. If the page is blocked, redirecting or duplicated, fix that first.
The report says “Crawled – currently not indexed”. Does indexing help apply?
Not directly. That status means Google already fetched the page. The next step is to look at the fetched version, duplication and canonical choice, and whether the page answers a query people actually make.
How do I check whether anything changed?
Where you have access to the property, use Search Console's URL inspection and Page indexing report. Guangsuan states that the observation period and the reporting method are agreed before cooperation, and that for pages without property access the available verification route is confirmed in advance.
Should I request indexing for every new page?
Treat it as a tool for a small number of important, genuinely updated pages rather than a routine. Google notes that it recrawls pages automatically and that repeated requests for an unchanged URL are not what moves the process forward.
Sources
- Google Search Console Help: Page indexing report — the definitions of “Discovered – currently not indexed” and “Crawled – currently not indexed”, and guidance on why a URL may legitimately be left out of the index.
- Guangsuan's GSI page — the published scope, the batch sizes, the reference rates and the stated limits of the service.