Jump links and anchors: earning section links in results
Google can link straight to sections of a long page. Here is how heading ids and a table of contents make that more likely, and what you cannot control.
Some search results show a row of links under the title that jump straight to sections of the page. Google sometimes labels them "Jump to". They come from your page structure, and you cannot switch them on with a tag. You can make them more likely, and the same work helps readers and AI engines too.
What section links in results are
A jump link points at a fragment, the part of a URL after the # sign. The browser scrolls to the element with that id. When a page has clear sections with stable ids, Google can link to a section directly from the result.
Google's documentation describes these as something its systems may choose to show. There is no markup that forces it. Treat any advice that promises guaranteed jump links with suspicion.
What makes a page easier to split
Google has said that sections are easier to link when the content is well organized and the anchors are visible on the page. That points to a few plain habits.
- Give every h2 and major h3 a unique, stable id attribute.
- Write headings that describe the section, not clever teasers.
- Keep each section about one idea, so the link target makes sense alone.
- Use a table of contents near the top that links to those ids.
- Make sure the anchors exist in the server-rendered HTML, not only after scripts run.
None of these is a ranking factor. They are signals that a long page has a real structure.
Build a table of contents that works
A table of contents is the easiest way to expose your anchors. It is a list of links, each pointing to a heading id. Readers use it to skim, and crawlers see the same links.
- Add an id to each heading. Use short kebab-case words that match the heading text.
- Never change an id after publishing unless you have to. Old shared links and any indexed section links will break.
- List the headings near the top of the page as plain anchor links.
- Click every link and confirm the page scrolls to the right place.
- Check that a fixed header does not cover the heading after the scroll. CSS scroll-margin-top fixes this.
Do not hide the list behind a script
If your table of contents is built by JavaScript after load, a crawler that skips rendering will not see it. Generate it on the server when you can. The same logic applies to the ids themselves.
Common mistakes
- Duplicate ids on one page. The browser jumps to the first match, and the links become unreliable.
- Ids generated from random strings that change on every build.
- Tabs or accordions that hide the target section, so the jump lands on nothing visible.
- Fragment links used for navigation in a single-page app without real URLs behind them.
- A table of contents that lists headings the page no longer has.
What this means for AI engines
AI answer engines split pages into passages before they retrieve anything. Clear headings and one idea per section give them cleaner passages to pick from. Some products link to a specific passage in the cited page, using fragment links or text fragments. How often they do this varies by product and changes over time, so do not build a plan around it.
The low-risk view: a page that is easy to jump around in is easier for people, and probably easier for machines. The cost is small.
How to check your pages
Search for your own page and look at the result. Section links come and go by query, device, and page, so check a few queries. In Search Console, the performance report will not break out jump links as their own feature, so you cannot measure them directly. Click-through to a fragment URL may show up in your analytics as a normal visit to the page.
Takeaway
Pick your three longest pages. Give every heading a stable id, add a server-rendered table of contents, and test each link by hand. Then leave the ids alone. You are not chasing a feature. You are making a long page easy to navigate, and that is worth doing either way.