linuxdot.org Linux Expo Birmingham 2002
Linux news | Newbie's Linux manual | Linux links | Link us
The Linux columns | Book reviews
  DistroWatch + TuxReports November 30, 2002

The SEO Tools Worth Bookmarking for Quick Site Checks

Most site problems are found by a handful of small checks, not by a monthly report. A page that vanished from results, a redirect that loops, a sitemap that lists dead URLs and a title that got cut off all show up in minutes if the right utility is one click away. The trick is keeping the short list short.

What a quick check should answer

A good quick check answers one question in under a minute. Is this page indexed. Does this URL redirect where it should. Does the sitemap contain what I think it contains. If a tool needs a long setup or a login before it answers, it belongs in the occasional audit toolbox, not on the bookmarks bar.

A bookmarked set of SEO tools that runs in the browser fits that rule well, because nothing has to be installed and nothing has to be uploaded. The SEO.Domains toolkit, for example, groups its free utilities by job, such as sitemaps, keywords, content and domain research, which makes it easier to find the right one when a question comes up.

Write down the five questions you ask most often, then bookmark one tool for each. Anything beyond five tends to go unused, and the extra clutter makes the useful ones harder to spot.

Prefer tools that show their working. A result you can verify by eye, such as a status code or a list of extracted URLs, builds trust, while a single unexplained score invites guesswork.

Indexing and visibility checks

The first question in almost every investigation is whether Google can see the page at all. Google's own SEO Starter Guide suggests that you search for your site with the site operator and use the URL Inspection tool in Search Console to check how Google sees a page. Both are free, fast and authoritative, so they sit at the top of the folder.

The same guide notes that Google primarily finds pages through links from pages it has already crawled, which explains why a new page with no internal links can stay invisible for weeks. A quick check of internal links pointing at the page often explains a missing listing faster than any technical audit.

Keep the expectation realistic. The guide also warns that every change takes time to be reflected, so a check that shows no change an hour after an edit proves nothing. Record the date of each change and look again after a few days.

On-page and snippet checks

Title and description problems are the easiest wins and the easiest to catch. A snippet preview tool shows how a title will be truncated and whether a description reads well. Paste the text, adjust until the key words appear early and the meaning survives the cut, then publish.

Add a heading checker to the folder. A page with two competing main headings, or none, confuses readers and crawlers alike, and a quick extraction of headings from a URL shows the problem at a glance. Content tools that count words and characters also help keep titles within sensible limits.

Structured data generators belong here too, as long as the output is checked before it goes live. A generator saves typing, while a validation step catches the mistakes that generators sometimes introduce.

Check how a page looks when shared, too. Social previews pull titles, descriptions and images from the page, and a quick preview tool shows whether the result is readable before the link goes out. A fix takes minutes and improves every future share.

Redirect and sitemap checks

Redirect checkers show the status code and the chain of hops for a URL. They answer whether a permanent move really returns the right code, and whether a page passes through three redirects before landing. Fixing a chain takes minutes once it is visible, and the speed gain is immediate.

Sitemap utilities do the boring but valuable work. A generator turns a list of URLs into a valid file, an extractor pulls the URLs back out of an existing one, and a sitemap index builder combines several files into one. Running the extractor against a live sitemap is a fast way to spot URLs that should no longer be there.

Compare the sitemap with a crawl or with the pages that earn visits. Any URL that appears in the sitemap but returns an error is a quick fix, and any important page missing from it is a quick addition.

Use a bulk status checker when you migrate or rename pages. Paste the old URLs, read the response codes and look for anything that is not a clean single redirect. A list of fifty URLs checked in one go replaces an afternoon of clicking.

Schedule a monthly sitemap review. Sites change, plugins add and remove URLs, and a file that was correct in spring can carry hundreds of stale entries by autumn. Ten minutes with an extractor and a status checker keeps the file honest.

Keep a list of the fixes you make, with dates. The list becomes a record of how the site changed, and it helps when a ranking shift needs an explanation.

A bookmark folder that stays useful

Organize the folder by question, not by tool name. Labels such as is it indexed, where does it redirect and what does the sitemap hold remind you what each link is for, and they keep the folder usable months later when the tool names have faded from memory.

Review the list twice a year. Remove anything you have not opened since the last review, add a tool only when a real question has gone unanswered, and note the date of the last check on any tool you rely on. A small, current folder beats a long, stale one every time.

Share the folder with the people who work on the site. A common set of tools means everyone reaches for the same checks and describes problems the same way, which saves time in every conversation about what went wrong. A shared folder also makes onboarding faster for new colleagues, who can start checking things on day one.

About us  
Latest stable kernel: 2.4.20 | Latest development kernel: 2.5.50
Copyright © 1998-2002 Linuxdot.org.
Linux ® is a registered trademark of Linus Torvalds.