Trusted by 10,000+ marketers

  • Private planning
  • Instant access
  • Publication insights

Find your next useful tool

Popular tools and guides

Technical SEO

A responsive article-page QA checklist

Check an article at narrow mobile, tablet and desktop widths with the same content and interactions. Readability depends on line length, spacing, headings and working controls, not just a lack of horizontal scrolling. Test the sidebar and tables with real long titles rather than a short sample.

Illustration of technical tools, gears and chart bars

The short answer

Check an article at narrow mobile, tablet and desktop widths with the same content and interactions. Readability depends on line length, spacing, headings and working controls, not just a lack of horizontal scrolling. Test the sidebar and tables with real long titles rather than a short sample.

A worked example

A fictional guide uses a desktop table of publication criteria. On a small screen the table should remain understandable without pushing the entire page wider. The contents list can move above the article rather than shrinking the text. A 320-pixel test with the longest heading will expose issues a desktop screenshot cannot show.

A practical checklist

  1. Test common narrow and wide viewport sizes and the exact layout breakpoints. Look for clipped buttons, overflowing URLs and headings that compete with the page title.
  2. Use keyboard navigation to reach the contents links, article actions and footer. Keep visible focus states and meaningful link labels on every layout.
  3. Check a long article and a short one with images unavailable. Verify that reading order remains sensible when the desktop sidebar stacks into the mobile flow.

What to avoid

Avoid calling a design pixel-perfect after inspecting only one screenshot. Supplied references guide the typography, color and hierarchy, but real content lengths and responsive behavior require their own checks. Preserve accessible labels even when a compact visual design is used.

A useful follow-up

Should mobile text be much smaller to fit the design?

No. Reflow the layout and simplify spacing before shrinking essential reading text to fit a desktop arrangement.

Editorial note. Review the stated author, sources and publication scope before applying this guidance. Examples are illustrative, not customer results. No ranking, citation or commercial outcome is guaranteed.

Continue with context

Related reading

A canonical URL checklist for a rebuilt website

Choose the intended public URL for each article and make its canonical metadata consistent with that destination. A canonical identifies the preferred equivalent version; it is not a shortcut for merging unrelated pages. Review URL choices before migration rather than relying on whatever route happens to render first.

Read the guide ↗

Internal links that make an article library easier to use

Link to the next explanation a reader is likely to need, using text that describes the destination. A related-reading list should connect different useful tasks rather than repeat the same question on several pages. Build navigation from the reader's decision path, not an arbitrary link quota.

Read the guide ↗

Noindex and robots.txt are different controls

Use the correct control for the actual goal: managing crawler access is different from excluding a page from search indexing. Google's documentation distinguishes robots.txt from a noindex directive. A development preview should have an explicit indexing policy, not an accidental combination of unrelated rules.

Read the guide ↗