WEB BUILDER / READING A GUIDE

What makes a long guide easy to read.

A table of contents, a reading progress bar, an author box, related guides and sharing. Each one is optional, accessible and respects reduced-motion settings.

Why the reading layout matters for AI search

AI assistants and search engines can quote a guide more easily when it is easy to scan: clear headings, a direct answer near the start and sections a reader can jump to. The blocks on this page help with what sits around the text: a table of contents built from the headings, who wrote the guide and links to related guides.

Reading progress

A thin bar at the top of the screen shows how far through the guide the reader is. With reduced motion turned on, it jumps to each new position instead of sliding.

Table of contents

The table of contents is built from the guide's own headings. On a wide screen it stays at the side, as on this page; on a phone or in a short guide it sits at the top.

Author box

Who is behind the guide, with links to learn more or get in touch.

At the end of a guide, a list of other guides on the same subject, as a grid or a list. Here it shows three guides published on this site.

Sharing

The share bar uses the phone's own share menu where there is one, copies the link and shares to X and LinkedIn. Bluesky, Mastodon and Reddit can be added; this example adds Bluesky.

Sign-up form

Web Builder also has a sign-up form for the end of a guide. This site has no newsletter, so the form is not shown here.

Five more example pages.

← Templates · Page openings · Explanation blocks · Marketing blocks · Movement

Tell us what needs doing.

Amazon work, a question for a consulting session or a process worth automating. We reply with the service that fits.