# 4 March: New link styles, broken URL insights, a new integration and more

## ✨ New and noteworthy

### Change your link style

You can now switch between two link design styles for your published content — **Default** or **Accent**.

Default uses the existing design, with your links highlighted in your primary or tint color. Accent will simply add a colored underline to the link, with the text itself remaining the same color as the rest of your content.

<figure><img src="https://2672413337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPGZZo1PCN4rYgFLPD8Cl%2Fuploads%2FhynldMNfOjIZmH6pfqN2%2Flink-styles.jpg?alt=media&#x26;token=9f8b5d8d-53f5-4163-8a0a-20aab99df980" alt=""><figcaption></figcaption></figure>

This is the latest design update, following on from the [new hint blocks](https://gitbook-v2-j9bntc9oe-gitbook.vercel.app/url/gitbook.com/docs/changelog/february-2025/25-february-new-and-improved-hint-blocks) and [revamped customization options](https://gitbook-v2-j9bntc9oe-gitbook.vercel.app/url/gitbook.com/docs/changelog/february-2025/19-february-powerful-new-themes-site-section-groups-and-more) we’ve released in the last few weeks.

### Track URLs generating ‘Page not found’ errors

We’ve added a new **Broken URLs** section to your site’s **Insights** page. It shows any incoming links from external sources that are resulting in a ‘Page not found’ error. These may be incorrectly-inputted URLs, outdated links with no redirects, or spam links.

You can combine this with [site redirects](https://app.gitbook.com/s/NkEGS7hzeqa35sMXQZ4X/publishing-documentation/site-redirects) to point people looking for information in the right direction.&#x20;

And if you want to check the source of the broken URLs, you can head to the main **Traffic** insight section, filter by ‘Page: not found’ and scroll down to the **Referrers** section to see the source of the links.

### New Gurubase integration

We’ve just added [Gurubase](https://www.gitbook.com/integrations/gurubase) to our list of [GitBook integrations](https://www.gitbook.com/integrations) — so you can now add an AI-powered Gurubase chat widget to your documentation. The integration enables real-time AI assistance for your readers directly within your documentation pages.

<details>

<summary>Improved</summary>

* Last week, we talked about adding tables, quotes and hints to expandable blocks. Now you can also add reusable content to expandable blocks. We’ve also fixed the insert palette within expandable blocks, so hitting <kbd>/</kbd> on an empty line in an expandable block will now open it again as expected.
* We’ve raised the limit on footer groups and links per footer group from 4 to 16 to give you more flexibility when building a complex site.
* We improved the cards that appear during the site creation flow, to make them easier to browse and understand.
* Anchor links got some attention this week too. First, clicking an anchor hash will now scroll smoothly to that block rather than jumping. Plus, clicking the selected anchor hash again will remove it from the URL in your browser’s address bar, to give you a clean link to the top of the page.

</details>

<details>

<summary>Fixed</summary>

* Adjusted the hint spacing and text size for the new hint block designs.
* Fixed the table of contents collapse toggle so it's now sticky even when you scroll — which means you can show or hide the TOC even if you’re at the bottom of a long page.
* Fixed incorrect insight calculations in the overview cards for recently-created sites.
* Fixed a bug that allowed options in a palette to be activated multiple times in a row. Now the option is disabled once you’ve selected it for the first time.
* Fixed a bug in blocks with an anchor hash that meant you couldn’t select the content of a block by tapping on a trackpad.&#x20;
* Fixed an issue where hidden pages would not show in diff view.

</details>

***

We’re constantly working to improve the way you and your team work in GitBook, and value your input on features, bugs, and more. Make sure you head to our [official GitBook community](https://github.com/GitbookIO/community) to join the discussion.
