# Section links in search results
**URL:** https://discourse.julialang.org/t/section-links-in-search-results/80186
**Category:** Tooling
**Tags:** documentation
**Created:** [April 28, 2022, 4:27am UTC](https://discourse.julialang.org/t/section-links-in-search-results/80186 "2022-04-28T04:27:03Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@gustaphe](https://discourse.julialang.org/u/gustaphe)
#### Post date: [April 28, 2022, 4:27am UTC](https://discourse.julialang.org/t/section-links-in-search-results/80186/1 "2022-04-28T04:27:03Z")
When searching for something with duckduckgo or Google, I often stub my toe on this problem, example:
I search for `julia customizing broadcasting` and scroll down a bit. It finds [Interfaces · The Julia Language](https://docs.julialang.org/en/v1/manual/interfaces/), with a description that sounds very helpful:
> Customizing broadcasting Broadcasting is triggered by an explicit call …
But clicking the link brings me to the _top_ of Interfaces, and I have to find-on-page to get to the part quoted in the blurb.
What would have felt much more natural is for the link in the search results to be [Interfaces · The Julia Language](https://docs.julialang.org/en/v1/manual/interfaces/#man-interfaces-broadcasting) (with section link)
Is it possible to convince the search engine crawlers to do this?
---
### Author:  [@woclass](https://discourse.julialang.org/u/woclass)
#### Post date: [April 28, 2022, 6:14am UTC](https://discourse.julialang.org/t/section-links-in-search-results/80186/2 "2022-04-28T06:14:41Z")
> For example:
>
> > [https://www.example.com/RunningShoes/Womens.htm?size=8#info](https://www.example.com/RunningShoes/Womens.htm?size=8#info)
>
> A fragment (in this case, `#info` ) generally identifies which part of the page the browser scrolls to. Because the content itself is usually the same regardless of the fragment, _search engines commonly ignore any fragment used._
>
> [SEO Starter Guide: The Basics | Google Search Central | Documentation | Google Developers](https://developers.google.com/search/docs/beginner/seo-starter-guide#understandurls)
So it looks hard to do.
---
### Author:  [@gustaphe](https://discourse.julialang.org/u/gustaphe)
#### Post date: [April 28, 2022, 6:36am UTC](https://discourse.julialang.org/t/section-links-in-search-results/80186/3 "2022-04-28T06:36:12Z")
Hm. I wonder why this interaction annoys me so much more than other sets of documentation I know. Perhaps these long pages should be broken up into subpages? Or maybe it’s just me.
---
### Author:  [@woclass](https://discourse.julialang.org/u/woclass)
#### Post date: [April 28, 2022, 8:38am UTC](https://discourse.julialang.org/t/section-links-in-search-results/80186/4 "2022-04-28T08:38:53Z")
> [@gustaphe](#):
>
> Perhaps these long pages should be broken up into subpages?
Perhaps we can organize the document in another form.
> **[Diátaxis](https://diataxis.fr)**
>
> The Diátaxis framework solves a problem of quality in technical documentation, describing an information architecture that makes it easier to create, maintain and use.
When people search on Google, they want to find how-to guides for specific questions.
The existing documentation provides detailed information about the interface.
We could reorganize the documentation in the form of a how-to guide, and add some new pages.
The newly added pages focus on solving a single problem, which also makes it easier for search engines to crawl.