What's an internal link?
An internal link is a hyperlink that points to a page or resource within the same website domain. In other words, when you click on an internal link, the destination page is within the same website you were originally on. Internal links are typically used to direct users to other relevant pages or content within the same website. They are important for site navigation and can improve user experience and search engine optimization.
Why are internal links important?
Internal linking is important for SEO because:
- It helps search engines to understand the structure of your website.
- It spreads authority throughout your site, as the more internal links a page has, the more value it is perceived to have.
- It encourages users to spend more time on your website and visit more pages, indicating to search engines that the content is valuable and relevant.
- It helps to establish a hierarchy of importance and relevance among your pages.
- It can help to improve the indexing and crawling of your website by search engines.
- It can help to reduce bounce rates by directing users to related content on your site.
What's the update? And why's it feel like this article's AI generated?
The first 2 sections are AI generated because it's generic information. If you want to have AI-generated information that's specific to the points you want to make, you can use Wraith Scribe's long description option so you can inject your own unique ideas and the AI will expand upon it for you.
Anyway, most AI article generators out there don't include internal links, and those that do simply do keyword matching to some important keywords to some blog title that you have.
Wraith Scribe does it a bit differently.
Instead of just brute-forcing keywords, which may work better in the early 2000s, SEO has advanced from that. Google can very easily understand the actual meaning behind the words, so synonyms, or things that have similar meaning is considered relevant.
So, instead, Wraith Scribe:
- Scans all the text in the AI-generated article.
- Cross-references them against every section of every blog post, page, or category page that you have.
- Internally links them to either your blog post/page, or if you have a theme that gives your H2/H3 id tags, it'll link to a specific section of a specific post, making your internal links as relevant as possible. This boosts engagement since your reader won't have to scroll around the page for the information, and instead will be taken directly to the H2 or H3 that talks about it.
As an example, the following internal link on a test site:
Directly maps to a specific H2 where they talk about Ryan Serhant's time management system.
Here's what the new pipeline looks like:
As with the 1st version of anything, it works nicely (about 1-3 internal links per 1k words), but it's also kind of 'meh.' Some improvements I plan on making:
- Making article generation faster. Right now, my server doesn't have enough memory so some hardware upgrade or software architecture changes are needed.
- Have more links. I'd like to try to aim for 2-5 internal links per 1K words instead. I actually coded up 2 versions of this in the background. 1 version (current version) that lets you have 1 internal link maximum per H2 or H3. Another version whose limit is per sentence. But currently, I only released the 1st version because erring on the side of too few internal links is better than too much, according to this article. Namely, too many links can mess up how the crawlers think about how your website should work, and so more isn't better. It's more a fine balance between too many internal links vs. good engagement for your readers. That said:
- Allow for manual internal link generation. You can do this now in our editor with ctrl/cmd+k to add links easily, but if you don't want the AI to automatically build links for you, we want to allow you the option to upload your own spreadsheet to be able to map your internal links (i.e. you went to Ahrefs, found the best keyword<->url mappings for your site and you just want to use that as a constant instead). This will give you more control on how the internal links are mapped.
There are many other improvements that can be done too, but I'll leave that as a surprise. The current features don't really support those improvements I'm thinking about so I'll need to build those features first.