Urgent.News

What's breaking now, across thousands of outlets.

Tech

What a URL-Only Brand Audit Can Actually See: Build a Tiny Checker in Python

There are a lot of "free AI brand audit" tools now. Before trusting any of them, it helps to know what a tool can actually see when all you give it is a URL. Short answer: less than you think, but more than nothing. I help build one (a free URL-based brand audit tool called Vibe Checker), and this post is the honest version of how the inputs work, with a tiny checker you can run yourself. What is…

A URL-only brand audit tool like Vibe Checker can reveal some information about a website based on a single HTML fetch. The tool extracts the page title, meta description, Open Graph tags, the first H1 heading, visible text above the initial screen cut-off, buttons and links resembling calls to action, image alt text, linked stylesheets and font families, and inline colours if present.

However, a URL-only audit cannot retrieve computed colours, real layout, content above the fold on a mobile device, or any content injected by JavaScript. If the website is client-rendered, crawlers and AI assistants may see minimal information.

The Python script for Vibe Checker uses regular expressions to identify call-to-action (CTA) words, hype words, distinct call-to-action buttons, and Google fonts. The script returns a dictionary containing the title, number of H1 headings, the first two H1 headings, meta description truncated to 160 characters if available, number of words in the HTML, hype words found in the first screen, sorted list of distinct CTA buttons, and the set of Google fonts used.

To run the Vibe Checker, save the script as `check.py` and execute it with the desired URL as the command-line argument. The output will display the extracted information in a formatted manner.

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

Modelling a Custom Jewellery Order as a State Machine (with Human Approval Gates)

Custom jewellery orders are a nice, small example of why "add a chatbot" is the wrong first move for retail automation. The real problem is state: the customer wants to know where their order is, and…

  • Custom jewellery orders progress through defined states with human approval gates.
  • States include ENQUIRY, DESIGNAPPROVED, INMAKING, READYFORPICKUP, and DELIVERED.
  • Transitions require named staff member approval, with some triggering automated customer messages.

What I Had to Think About When Building a Product Launch Platform

Building a product launch platform sounds relatively straightforward. You need products. You need users. You need voting. You need a leaderboard. Done, right? Not quite.

  • LaunchStall platform tackles community rules and lifecycle complexities
  • Weekly edition system with predictable phases from Monday to Sunday
  • Free path offers LaunchStall badge, paid plans remove requirement

Write the Acceptance Tests Before the Agency Writes the Automation

If you are the technical person asked to "work with the agency", here is the one thing I would do before kickoff: write the acceptance tests yourself, in plain language, and attach them to the…

  • Write acceptance tests before agency writes automation.
  • Tests describe system response to specific real-world inputs.
  • Include unique identifier, condition, outcome, and human approval flag.

Stop Losing Work Mid-Job: Practical systemd-inhibit on Linux

You start a multi-hour rsync , walk away, and the laptop suspends halfway through. Or someone hits reboot while apt full-upgrade is unpacking.

  • Systemd-inhibit prevents interruptions during long-running Linux tasks.
  • Inhibitor locks block sleep, shutdown, idle actions, and power/lid key handling.
  • Systemd-inhibit command creates a file descriptor to automatically remove the lock.

More from Wednesday 7 October →