Page inspector
Click any row in the results table and the page inspector opens as a drawer beside it. Each tab presents a different slice of what Consuela found for that URL: metadata, content metrics, links, images, social previews, technical details, and — when the data exists — rendering analysis, redirect chains, structured data, and inbound links.
The header of the drawer mirrors the row it was opened from: the URL, the status code badge, the content type, and the crawl depth. Everything below is organised into tabs.
SEO
The SEO tab collects the on-page signals that search engines read first.
Content
The Content tab presents the metrics that describe the body of the page rather than its metadata.
Links
The Links tab opens with two metric tiles showing the internal and external link counts for the page, followed by a table for each category.
Internal links
Each row shows the destination URL, the anchor text (or "(empty)" when
none was set), and the link type — the HTML element the link came from,
such as a, area, or
link. Up to 100 entries are displayed; when the
page has more, a line below the table states how many were omitted.
External links
External links follow the same layout but show the
rel attributes instead of the link type. Values
like nofollow are highlighted to make
sponsored or untrusted links easy to spot. Up to 100 entries are displayed.
Images
The Images tab starts with two metric tiles — total image count and the number missing alt text. When any images lack alt text, a severity badge states how many need attention.
Below the summary is a table with up to 100 rows:
Social
The Social tab previews how the page will appear when shared on platforms that consume Open Graph or Twitter Card tags.
Open Graph
A preview card renders the og:image,
og:title,
og:description, and
og:site_name the way a social platform would
display them. Below the card, every Open Graph tag found on the page is
listed as a property-value pair. When no OG tags exist, the section says
so.
Twitter Card
A second preview card renders the Twitter Card tags. The layout depends on
the twitter:card value: a
summary card uses a small square thumbnail
floated beside the text, while
summary_large_image uses a full-width image
above it. Below the preview, the
twitter:card,
twitter:title,
twitter:description, and
twitter:image values are listed.
Technical
The Technical tab presents the HTTP and document-level metadata:
Conditional tabs
Four additional tabs appear only when the relevant data exists. They stay hidden rather than showing an empty panel, so the tab bar reflects what the page actually has.
Rendering
The Rendering tab appears for pages that were analysed with headless Chrome. It is divided into three sections:
- Rendering findings — issues detected during the browser render pass.
- Mobile findings — mobile-specific issues with an overall mobile score. The score is Consuela's own measurement, not a Lighthouse score, and a note below it says so.
- Resource findings — issues with the resources the page loaded, with total request count and transfer size.
Each finding carries a severity badge (critical, warning, or notice), a label, and a detail line. When a section has been analysed and no issues were found, it says "No findings" — this is distinct from the message shown when a page was never analysed at all, which explains why the analysis is absent rather than claiming the page is clean.
Redirects
The Redirects tab appears when the page resolved through one or more redirects. A banner at the top states the number of hops, and warns when the chain is three or more hops long.
Below the banner, the redirect chain is visualised as a vertical sequence of cards. Each hop shows:
- The HTTP status code (301, 302, 307, 308).
- The redirect type (e.g. Permanent, Temporary).
- The URL at that hop.
SEO warnings appear inline: temporary redirects (302, 307) note that a 301 may be more appropriate, and hops beyond the third are flagged for performance. The chain ends with a "Final" destination card showing the resolved URL.
Structured Data
The Structured Data tab appears when the page contains JSON-LD, Microdata, or RDFa markup. It has up to four sections:
- Validation issues — each issue shows a severity badge (Error, Warning, or Info), the Schema.org type and property involved, a message, and when available a suggestion and a link to documentation.
- JSON-LD blocks — each block is marked Valid or Invalid, lists its Schema.org types, and can be expanded to show the raw JSON. Parse errors are listed above the raw content.
- Microdata items — listed by
itemtype, with each property and its values. Nested items are indented. - RDFa items — listed by
typeof, with each property and its values.
Inbound Links
The Inbound Links tab appears only for pages returning a 4xx or 5xx status code. It answers the question "which pages link to this broken URL?" by listing every page in the crawl that contains a link to it. Each row shows the source page's title, URL, and the anchor text of the link. This makes it straightforward to find and fix or remove broken references.