rekby67 downloadsDisplays anchor icons next to headings targeted by internal links and lets you navigate to every note that references each heading.
Читайте на русском: README.ru.md.
An Obsidian plugin that shows an anchor icon in the editor gutter next to headings that are targeted by internal links ([[Note#Heading]] or [[#Heading]]). Click the icon to open a menu of all notes that link to that heading, then jump straight to the exact link line in the source file.
# fragment pointing at a heading. Builds a map of “which headings are linked from where.”line: quote entries.[[#Heading]] / [[#Some heading]] style links where the target is a heading in the same note.![[Note#Heading]] style embeds are counted the same as ordinary [[...]] links.[[My note#Introduction]], or in the same file: [[#Introduction]].Tip: The plugin matches headings by normalized text (trimmed, collapsed spaces, case-insensitive), consistent with how link fragments refer to heading titles.
Anchor icons in the gutter
Referenced headings show an anchor in the left gutter; headings without incoming header links have no icon.
![]()
Context menu
Click an anchor to list every note that links to that heading, then jump to the exact link you need.

Note: This method will be available after the plugin is accepted into the Obsidian community plugin list (PR). For now, use BRAT or manual installation below.
If the plugin is not yet in the community list or you prefer installing from GitHub:
https://github.com/rekby/obsidian-header-backlinksmain.js, manifest.json, and styles.css from the latest release.<Vault>/.obsidian/plugins/header-backlinks/.npm install
npm run dev # watch mode
npm run build # typecheck + production bundle
npm run lint # ESLint
Regenerate English and Russian README screenshots and demo GIFs (requires a local Obsidian test setup configured for WebdriverIO and ffmpeg for GIF encoding):
npm run demo # screenshots (docs/demo/ + docs/demo/ru/) + GIFs (docs/demo/*.gif + docs/demo/ru/*.gif)
npm run demo:screenshots # README PNGs only (both languages, one run)
npm run demo:capture # demo frame capture + manifests (EN + RU); then `npm run demo:render` for GIFs
npm run demo:screenshots:ru # Russian README PNGs only (faster iteration)
#fragment) are considered, not block references (^block-id).See LICENSE.