Urgent.News

What's breaking now, across thousands of outlets.

Tech

The smallest SEO loop for a static tool site

Tool sites generate many similar URLs. The pieces below are the ones that change indexing and share cards. Examples are taken from the public HTML of Colorful Toolhub . The generators live on the SEO Marketing workbench and run in the browser. One title and description per URL The home page title is "Colorful Toolhub by Snamibo - Free Online Tools Collection", and the description names 1,400+…

Static tool sites have numerous similar URLs. Key URL elements influencing indexing and share cards include title, description, canonical link, viewport, Open Graph, and hreflang. Each indexable URL requires a rel=canonical pointing to the desired indexed page. Mobile-friendly pages benefit from a viewport meta tag, while social media share cards utilize Open Graph tags.

Titles should be around 60 characters, focusing on the page topic before the brand. Descriptions should be 150-160 characters, with an empty description causing search engines to quote navigation or a random tool name. Every page must have a rel=canonical to its designated URL. Search URLs like /?q= should redirect to a stable page.

The Meta Tag Generator provides title, description, canonical, and viewport data, with viewport being essential for mobile-friendliness. Open Graph tags set the share card image and card type, while hreflang specifies paired language versions of the site. Robots.txt and sitemap.xml define crawlable URLs, excluding site search and session parameters.

JSON-LD markup should reflect the page's actual functionality, with search actions only included if the query string performs a search. Campaign parameters should not appear in canonical URLs, and a correct tag set may still display the previous version for days after deployment.

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

Day 5: We scanned a 200-route codebase into OpenAPI without uploading a file

Days 2 through 4 covered the easy case: a new API where the spec can come first. Most of us live in the other case. The service is three years old, the original team is gone, the docs are a Postman…

  • Powerduck scanner scans 200-route codebase into OpenAPI without uploading files
  • AST scanner combined with human review proves most effective for large codebases
  • Scanner maintains privacy by running entirely on local machine

Four CSS bugs my headless tests couldn't see

I test Cá Viên Chiên mostly with headless Playwright: walks over every screen at several widths, layout measurements, screenshots. That catches a lot.

  • Minifier issue caused blurred header button
  • Header button hidden by sliding down on hover
  • Safari fade-in animation had flickering glitch

More from Saturday 3 October →