Reply to thread

Message: [QUOTE="Queen, post: 90487, member: 27"] The URL Inspection API gives you two thousand checks a day per site, and the Search Analytics endpoint returns twenty-five thousand rows per request. Both are free. Almost nobody building their first tool touches either one. The instinct is to build something that looks impressive, with charts and a sidebar and a login screen. That is the wrong first project. The distance between a tool that reports a problem and one that gets it closed is what [B][URL='https://goldmidi.com/community/threads/any-zimbweans-here-who-are-into-vibe-coding-and-seo.75864/post-90431']a desktop app built around assigned work and verified outcomes[/URL][/B] is aiming at, and charts are not how you cross it. The tools that pay you back are the ones that replace a job you currently do by hand every week, badly, at eleven at night. Design them around the quota rather than the interface. Once you know the ceiling on an API, the shape of the tool decides itself. [HEADING=2]Start with the export nobody wants to do by hand[/HEADING] Search Console will hand over its performance data through the Search Analytics endpoint, grouped by query, page, country, device, date, hour, or appearance in results. One request returns up to twenty-five thousand rows, and a zero-based start row lets you page through the rest. The per-site allowance runs to twelve hundred queries a minute, which no small operation will ever exhaust. So build the pull once. Write the rows to a dated file, compare today against yesterday, and print only what moved. That is fifty lines of code, and it turns a twenty-minute clicking exercise into [B]a check that runs itself before you wake up[/B]. Inspection is tighter. Two thousand URL checks a day per site sounds generous until you point it at a large catalog, so the tool needs a queue and a priority rule rather than a loop over every URL you own. Newly published pages first, then anything that changed, then a slow rotation through the rest. [HEADING=2]The file formats have limits worth checking[/HEADING] A sitemap file may hold no more than fifty thousand URLs and must stay under fifty megabytes once uncompressed, and a sitemap index has exactly the same two limits. Gzip helps with transfer, not with the ceiling, because the uncompressed size is what counts. Google parses only the first five hundred kibibytes of a robots.txt file and ignores everything after that. It caches the file for up to twenty-four hours, drops invalid lines rather than complaining about them, and may ignore characters outside the UTF-8 range, which can quietly invalidate a rule you thought was live. The rules also apply only to the exact host, protocol, and port serving that file. None of those failures announce themselves. A short validator that counts URLs, measures uncompressed bytes, and flags a robots file creeping toward the limit costs an afternoon and catches problems that otherwise surface months later. [HEADING=2]Submission and speed checks are cheap wins[/HEADING] IndexNow accepts up to ten thousand URLs in a single post, mixing HTTP and HTTPS addresses, once you host a key file at your root. The key runs between eight and one hundred and twenty-eight characters, and a key placed in a subdirectory only authorizes URLs under that path. Push too hard, and you get a 429 back, so batch sensibly and log what you sent. The PageSpeed Insights API runs with or without a key, though a key is recommended for automated querying, and it returns field data from the Chrome User Experience Report alongside lab results from Lighthouse. That field data is being discontinued inside the PageSpeed response, with the CrUX API and CrUX History API named as the replacement. Point any new build at the CrUX API directly. It costs nothing extra today, and it means the thing you write this month still runs next year. Log your own consumption against each allowance while you are at it. A tool that stops at nineteen hundred inspections and tells you exactly why beats one that dies at two thousand and one with a raw error, especially when you are running it for someone who pays you. [/QUOTE]

Name