FAQ

Frequently asked questions

Indexing & Google

No. Nobody can. Google controls crawling and indexing. We prepare URLs technically, assist legitimate discovery (sitemaps, feeds, internal links) and report Google's own verdicts through the URL Inspection API.

Only through the official Google Search Console URL Inspection API, for properties you connected and selected. The verdict, coverage state and last crawl time are stored for every inspection.

We have no verified data. Either you did not connect Search Console, the URL is not inside a selected property, or the inspection has not run yet. It is not a negative result.

No. The URL Inspection API only works for properties the connected Google account is authorised to access. We do not claim otherwise.

Working pages submitted in the last days that are not in Google yet are listed on public pages and feeds of this site (/links, an RSS feed and a sitemap). When Googlebot crawls this site it can follow those links to your pages. It helps discovery; it does not guarantee indexing.

Yes, when the administrator has connected service accounts. Google only accepts URLs on sites where our service account is an owner in Search Console, so it mainly helps pages on sites we manage.

When the administrator has switched it on, working links of your job are also listed in short posts on our own Telegraph, Blogger or Tumblr pages, which Google visits often.

Processing

Workers process URLs continuously in the background with polite per-host intervals. You do not have to wait for the whole batch — each URL updates individually and you can leave the page.

Yes. By default our crawler does not fetch URLs disallowed for it, and we additionally report whether Googlebot is allowed. We never impersonate Googlebot.

They are detected and reported with dedicated statuses and recommended next steps (for example: submit the final URL instead, remove the noindex directive).

Yes. Processing can be paused and resumed, pending jobs cancelled, and failed URLs or whole batches retried.

WordPress

No. The platform administrator connects the WordPress website(s) used for link placement. Regular users cannot connect arbitrary sites unless the administrator enables that feature.

Inside a visible, clearly delimited "Related resources" block appended to administrator-approved existing posts. Existing text, images, headings, formatting and links are preserved.

Yes. Every insertion is recorded and an administrator can remove a link with one click; the post is updated through the same REST API.

No. It may help discovery, but Google decides whether to recrawl the post and whether to index the destination URL.

Account & billing

One credit is consumed per URL queued for processing. Credits represent platform work, not outcomes.

If a URL is still not found in Google after the last scheduled index check (by default 14 days), contact us through live chat, WhatsApp or Telegram with the job number and we will return the credits.

Yes, a documented REST API with per-user keys, rate limits and usage logs. API access depends on your plan.

WordPress Application Passwords and Google tokens are encrypted at rest, passwords are hashed with Argon2id, sessions are protected against hijacking, and outbound fetches are guarded against SSRF.

Yes, from Account settings. Your personal data is anonymised and API keys / Google tokens are removed.

Still have a question? Contact us.