London Web Factory

SEO Spider LWF SEO Spider: Using the Browser and Page Analysis

The Browser tab is the main starting point for browsing, analysis and crawling.

Browser Controls

The toolbar includes:

Control What it does
Back Goes to the previous page in the in-app browser history.
Forward Goes forward in the browser history.
Reload Reloads the current page.
Home Opens Google.
Address bar Accepts website addresses and Google searches.
Analyse page Analyses the currently loaded browser page and opens the sidebar.
Start Starts crawling the current website.
Pause Pauses an active crawl.
Resume Resumes a paused crawl.
Stop Stops an active crawl.

Address Bar Suggestions

When you click into the address bar, the app can show previously crawled websites from the local crawl history database. The suggestions are based on crawls started from this installation.

The menu shows:

  • website host;
  • full crawl URL;
  • crawl count, when a website has been crawled more than once.

Typing in the address bar filters the suggestion list.

Page Analysis

Analyse page inspects the rendered page currently open in the Browser tab. The app waits for any current load to finish and then allows a short settling period before extraction. The result reflects the DOM that Chromium can see at that moment.

The Browser tab uses a persistent browser session, so cookies and local storage can affect what is analysed. The separate crawl session is cleared at the start of a crawl; Page Analysis and Crawl Results can therefore differ for a personalised or authenticated page.

While the Page Analysis sidebar remains open, it automatically analyses the next page after a full navigation, reload, Back/Forward action or URL-changing in-page navigation finishes. Closing the sidebar stops automatic analysis.

The sidebar includes:

  • title and title character count;
  • meta description and character count;
  • first H1;
  • rendered H1, H2, H3, H4, H5, H6, P, LI, A and TD element counts;
  • total words and words after stop-word filtering;
  • path;
  • image count and alt text counts;
  • load time and content type;
  • canonical URL;
  • robots meta;
  • first paragraph;
  • document outline;
  • top words and phrases;
  • links;
  • images;
  • robots.txt and sitemap.xml status.

Text and Phrase Analysis

The Words total counts whitespace-separated rendered body text after excluding text inside script, style, noscript, SVG, canvas and template elements. It can include menus, footers, cookie notices and other visible interface text.

For Top Words and phrases, the app then:

  1. lowercases the text;
  2. removes most punctuation;
  3. removes one-character tokens;
  4. removes a built-in set of common English stop words;
  5. counts individual words and adjacent two-word and three-word sequences.

Results are ordered by frequency, then alphabetically when counts tie. Phrase analysis is a way to inspect repetition and topic language; it is not a keyword-density recommendation or ranking score.

Element Counts

Element Counts reports the number of rendered <h1> through <h6>, <p>, <li>, <a> and <td> elements. These are raw DOM counts, so empty or visually hidden elements still count when they remain in the document.

A counts every anchor element, including anchors without a usable href. It is not the same calculation as crawl Outlinks. TD counts table data cells and does not include <th> header cells.

First Paragraph

First Paragraph is the first non-empty rendered <p> in document order. It is a literal DOM rule, so the result can be navigation, cookie or interface copy when that paragraph appears before the main content.

Document Outline

The Document Outline displays the first 80 non-empty rendered H1-H6 elements in document order. It is useful for checking whether the page has a sensible content hierarchy and whether important page sections are visible to the rendered DOM.

The outline does not include paragraphs, infer missing heading levels or decide whether the hierarchy is correct.

Links

The Links section displays the first 80 rendered <a href> elements. Each entry uses labelled lines:

  • Anchor Text: cleaned rendered anchor text;
  • Href: resolved destination URL;
  • Title: the optional link title attribute, when present.

This is a direct inspection list and is broader than the crawl's Outlinks calculation. It can include fragments and non-HTTP schemes that the crawler excludes from link metrics. See How Link Metrics Are Calculated.

Images

The Images section displays the first 80 captured elements from the rendered document.images collection. It shows each image as:

  • Alt: the image alt text, or a missing/empty alt warning;
  • Src: the image source URL;
  • Title: the image title attribute, where present.

Missing alt means the alt attribute does not exist. Empty alt means it exists but contains no non-whitespace text. Empty alt can be appropriate for decorative images. CSS background images are not part of document.images and are not listed.

Site Files

Page Analysis checks common site-level files for the current site:

  • robots.txt;
  • sitemap.xml.

Each request follows redirects, has a ten-second timeout and reads at most 80,000 characters. The app reports whether the response was successful and may show a text preview.

Found does not mean a robots or sitemap file is syntactically valid. It only means the request returned a successful HTTP response.

Analysis Collection Limits

Data Extracted Displayed in sidebar
Document Outline entries 300 80
Links 500 80
Images 300 80
Phrases of each length 25 10
robots.txt or sitemap.xml preview 80,000 characters 80,000 characters

What Page Analysis Does Not Guarantee

Page Analysis is a practical rendered-page inspection. It does not interact with the page, scroll to trigger lazy content, bypass consent or authentication, or guarantee parity with a search engine renderer. It does not predict rankings or traffic.

For the precise meaning of each sidebar value, see ...