The seven-stage pipeline, step by step
Each submission follows exactly this order. You never wait for a whole batch — results appear per URL as workers finish them.
User submission
You register, choose paste / file upload / single URL / API and submit. Limits from your plan apply. Credits are reserved: one per URL.
URL validation
Each entry is normalised (scheme, host, path), checked for format problems, private hostnames and unsupported ports, and de-duplicated. Invalid entries are listed in the report but never queued.
URL processing
Workers fetch each page safely: DNS is validated, private networks are blocked, redirects are followed hop-by-hop with validation, and the HTML is analysed for title, robots directives and canonical tags. robots.txt is respected.
Discovery assistance
Per host, the engine discovers public sitemaps (robots.txt + well-known paths), parses them, finds feeds and checks internal links from fetched pages and the homepage. Each URL gets flags: found in sitemap / feed / internally linked.
Google status
If you connected Search Console and selected a property that owns the URL, the official URL Inspection API runs and stores the verdict, coverage state, last crawl time and canonicals. Otherwise the status is honestly "Unknown".
WordPress automation
After the previous stages finish, eligible URLs (publicly fetched, not noindex) are queued for insertion into administrator-approved published posts of the configured WordPress site. Limits, intervals, duplicate checks and approval mode are enforced; every update is verified.
Final report
The submission report shows submitted, processed and failed URLs, discovery results, Google inspection results, WordPress insertion results and updated post details — exportable as CSV or TXT.