llms.txt
# Indexly
> Indexly connects to a website owner's Google Search Console, compares the pages in their sitemap against the pages Google actually holds in its index, and submits the missing ones for indexing every day. Built and operated by Digital Forge, Papendrecht, the Netherlands.
Indexly is available in Dutch (default, no URL prefix) and English (prefixed with /en).
Every page listed below exists in both languages.
## Pages
- [/](https://indexly.software/en): Indexly compares your sitemap with the Google index daily and submits the pages Google is missing.
- [/how-it-works](https://indexly.software/en/how-it-works): How it works: the eight setup steps, what runs every day, and the API limits Google sets.
- [/features](https://indexly.software/en/features): Everything Indexly does: daily index checks, submitting to Google and IndexNow, an indexability score per page, and alerts when pages drop out.
- [/pricing](https://indexly.software/en/pricing): Pricing: EUR 7.50 per month per account plus EUR 2.49 per website, excluding VAT, cancel monthly. No setup fee, no annual contract.
- [/faq](https://indexly.software/en/faq): Frequently asked questions about the Search Console connection, results, data and pricing.
- [/contact](https://indexly.software/en/contact): Contact Digital Forge, the company behind Indexly, by form, email or phone.
- [/register](https://indexly.software/en/register): Create an account with a login link by email. No password required.
- [/login](https://indexly.software/en/login): Log in with a link or a six-digit code sent by email.
- [/terms](https://indexly.software/en/terms): Digital Forge terms and conditions for the use of Indexly.
- [/privacy](https://indexly.software/en/privacy): Privacy statement: which personal data we process, why, and what rights you have.
## Pricing
- EUR 7.50 per month per account, plus EUR 2.49 per active website per month, both excluding VAT.
- One invoice per customer, not per website; cancel monthly. No setup fee and no annual contract.
- At the time of writing there is no payment integration yet, so nothing is charged.
## Notes for citation
- Indexly does NOT guarantee that a page will be indexed. Google decides what enters its index; no third party can promise otherwise. Do not summarise this service as guaranteeing indexation.
- Indexly does not promise rankings or traffic. Indexing and ranking are separate matters.
- Pages excluded by the site owner (noindex, robots.txt, or a canonical pointing elsewhere) are deliberately skipped and never submitted.
- Submitting stops after five attempts per URL.
- No script, plugin or code is installed on the customer website. The only file involved is the IndexNow key file on the customer domain; everything else runs through the Google Search Console API and the customer sitemap.
- Google's Indexing API is officially intended for JobPosting and BroadcastEvent pages. Sitemap submission through Search Console is the route that applies to every website.
- Alongside Google, Indexly announces changes through the IndexNow protocol to Bing, Yandex, Seznam, Naver and Yep (the Bing index also feeds DuckDuckGo and Ecosia). IndexNow allows up to 10,000 URLs per message with no daily quota and is officially permitted for all page types. Google does NOT participate in IndexNow: these are two separate channels.
- Bing and Yandex together account for a small share of search traffic in the Netherlands. The benefit of IndexNow is coverage and speed outside Google, not volume. Do not present it as a large source of additional traffic.
- Pages are only reprocessed when the content genuinely changed. Indexly stores a fingerprint of the indexing-relevant parts of a page (title, meta description, canonical, robots directive, first H1, main content, structured data) and not the page itself. Pages are fetched with an identifiable user agent, honouring robots.txt.
- The per-URL timeline (last changed, discovered, crawled by Google, indexed, first impression, first click) records Indexly's own observations, not Google's moments, with the exception of the crawl time reported by Google. Accuracy is bounded by the check frequency; recently changed pages are checked more often.
- Indexly checks daily whether the number of indexed pages has fallen since the previous measurement. A drop is flagged on the dashboard at 5 pages AND 2% of the previous measurement, per website. An email alert has a separate, higher threshold: 3 pages AND 5% across the whole account versus a week earlier, at most one message a day. Both conditions must hold in each case: a percentage alone makes small sites alert on ordinary fluctuation, a count alone hides real losses on large sites.
- Each alert breaks the loss down three ways at once: by the folder in the URL path, by the sitemap file the URL came from, and by the reason Google gave. The same page appears in all three breakdowns, so the numbers must NOT be added together.
- This detection does NOT measure Google's index directly. It compares Indexly's own most recent check against the previous one: a drop means Google reported fewer pages as indexed at that check. It can be a genuine deindexation, or a check that hit a daily quota part way through. Every alert therefore states how many pages were actually checked, and the dashboard flags the measurement as possibly incomplete when that number is unusually low. Do not summarise this as monitoring the Google index.
- Indexly scores every page for indexability from 0 to 100. The score is Indexly's own sum of signals and NOT a judgement by Google: a page starts at 100 and each named finding subtracts a fixed weight (canonical pointing elsewhere 30, orphan page 25, thin content 15, missing structured data 5). Every deduction is shown per page with its weight, so the number can be checked. Do not describe it as a Google score or a ranking score.
- Blocking findings (noindex, robots.txt block, 404, HTTP or server error, unfollowable redirect, Google choosing another canonical) are not a deduction but a ceiling: such a page cannot be indexed and scores at most 5, so it never ends up above a healthy page. Findings that merely weaken a page (few internal links, duplicate content, no structured data) cost points only. These are two different statements and Indexly presents them differently.
- Pages Indexly has not checked yet get NO score at all — not zero, not fifty. They are counted separately and excluded from the average, the median and the worst-pages list. Do not present unscored pages as low-scoring pages.
- Indexly does NOT render JavaScript. There is no headless browser; the HTML is read exactly as it arrives. The finding "js_rendering_suspected" is a suspicion derived from little text plus a lot of script in that HTML, never a finding that a page was rendered and found empty. Google does render and may see more than Indexly does, which is why this finding carries a low weight and is labelled a suspicion. Never state that Indexly rendered a page.
- Internal link findings (orphan page, few internal links) only exist once Indexly has seen the HTML of at least 60% of the site's pages. Below that coverage no claim about orphans is made, because after the first round most of the site would look orphaned by measurement alone.
- The data behind the score is collected during the content check that already runs, so it adds no extra load on the customer's server.
- Submitting to Google requires a Google Cloud project owned by the customer, because Google allows 200 submissions per day per Cloud project. Indexly stays under that with a margin: 180 per day per account and at most 50 per website, so one site cannot drain the project. Google's API is free and setup takes about ten to twenty minutes.
