Urgent.News

What's breaking now, across thousands of outlets.

Tech

I planted 370 SEO defects in a fake 400-page site to test an auditor

Everything below uses a site I generated. These are test results, not results from anyone's real website. The idea A crawl of your own site already holds most of what an SEO metadata audit needs: titles, descriptions, canonicals, language, Markdown (so headings), word counts. Crawling again to check them is a second bill and a second chance to get blocked. So I wrote an Apify Actor that audits…

I crafted a fake 400-page site, designed to test an SEO metadata auditor. The site, generated using a synthetic generator, contained hidden issue codes that the auditor was supposed to identify. Upon crawling the site, the auditor detected 370 issues across 54 distinct rule codes, including 50 errors, 238 warnings, and 82 information messages. The audit reported a site score of 94 (grade A), with 333 pages graded A and 67 graded B.

The auditor proved that the rules functioned correctly, reporting the expected issues and scoring the site accurately. However, it did not validate the auditor's accuracy on real sites, as it was based on the author's own generator, rules, and tests. Real crawls may have structures the author did not anticipate.

In terms of performance, the audit step took about half a second for 10,000 generated pages, and 4.0 seconds in total for 2,000 synthetic pages in the cloud. The slowest part was reading and writing the dataset, not the auditing process itself. The audit tool charges $1.50 per 1,000 pages and provides a prefilled example for testing purposes. If any issues or false flags are encountered while using the tool on a real crawl, the author encourages feedback.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

The Anatomy of CVE-2024-4577: Why You Shouldn’t Abandon PHP Over a CGI Best-Fit Code Page Exploit

When a critical Remote Code Execution (RCE) vulnerability hits a language that powers a large share of the web, the headlines predictably declare the death of the ecosystem.

  • CVE-2024-4577 is a PHP RCE vulnerability, not a flaw in modern PHP language.
  • Windows character-encoding mechanics and legacy CGI execution cause the exploit.
  • Upgrade to PHP 8.1.29+, 8.2.20+, or 8.3.8+; migrate from legacy CGI to PHP-FPM.

Turning Google Maps results into a CSV for a small outreach project

I recently helped a friend who runs a small web design studio build a list of local businesses to contact. The goal was simple: every bakery and cafe in two neighbourhoods, with phone, website and…

  • A web design studio aimed to compile local businesses for outreach.
  • GMB Scraper extension exported Google Maps data to CSV format.
  • Filtered for businesses without websites to identify potential clients.

How Amazon Handles Millions of Orders on Sale Day - The Engineering Behind It

It's Amazon Great Indian Sale. Midnight strikes. Millions of people hit refresh simultaneously. Your internet slows down. The app feels laggy.

  • Amazon processes 1.4 million items per minute during Prime Day 2024
  • Microservices architecture enables independent scaling of services
  • Eventual consistency allows instant cart additions during sale day

More from Saturday 24 October →