Skip to main content
Internal links connect one page on your website to another. In theStacc, Your Website Pages supplies candidate destinations for generated articles. Keep this list relevant and current, then review the links in the article preview. Matching a destination is different from checking that its page loads. The internal-link resolver uses your saved titles and URLs; it does not visit each destination to confirm its availability.

Your list of linkable pages

Each entry contains a page title and URL. Add public pages that help readers complete the task the article discusses, such as a related guide, service description or contact page. Give each page a distinct, descriptive title so it is easier to identify. A saved entry is a candidate, not an instruction to link to that page in every article. Check that the selected destination fits the surrounding sentence.

Where to manage the list

Open Content SEO > Settings > Preferences and turn on Include Internal Links. The Your Website Pages section appears while that setting is enabled. To add a destination:
  1. Click Add Page.
  2. Enter a descriptive Page title and the page’s URL.
  3. Click Add Page again to save the entry.
  4. Open the saved destination and confirm that it leads to the intended public page.
To remove an entry, hover over it and use the remove button. Adding or removing entries requires project editor access. Removing an entry from this list does not remove links from articles already published on your website.

Pages we add for you

A completed sitemap analysis can add recent blog URLs to the list. This import adds at most 20 new entries per run, skips URLs already recorded, and derives titles from the final part of each URL. It is not a complete inventory of your website. Review imported titles and destinations. Add useful service pages or older guides yourself if they are missing, and remove addresses that no longer represent the content readers need.

How links get added to a post

During generation, theStacc can mark an intended internal link with a reference such as [INTERNAL:booking-guide]. This is a temporary reference to a candidate page, not the address readers should follow. The link setting guides generation. It does not guarantee a fixed number of links, or that every reference will resolve to a suitable destination. Review the resulting article rather than treating a link count as a quality check. Preview and publishing use the project’s saved destinations to resolve these references. Exact matches to normalized URL slugs take precedence; exact title matches and sufficiently close, unambiguous matches can also be used. If a reference cannot be matched, supported forms lose the link while keeping readable text.

What to check in the preview

What to check in the preview

What you seeWhat it meansYour next step
A clickable internal linkA destination was selected from the saved list.Open it and check the page and its relevance.
The intended words appear without a linkThe reference may not have resolved to a usable match.Check the saved title and URL, then inspect the article again.
A raw [INTERNAL:…] reference or an unresolved-link publishing errorLink preparation needs attention.Correct the reference or replace it with an appropriate link before retrying.
The publishing paths checked for this guide include a final check that blocks content still containing an unresolved internal reference. That check does not establish that a resolved URL is live, current or relevant. Preview can also fall back to the draft if link preparation fails, so do not ignore a raw reference. For example, suppose your saved page is Booking Guide, with the URL https://example.com/guides/booking-guide/. An article’s booking-guide reference can resolve to that saved address. If the page is later deleted, matching the same reference does not discover the deletion. Update the saved destination and review affected articles. This example is illustrative, not a customer result.

Relative URLs become full web addresses

With a valid project website address, root-relative links such as /contact can be expanded for preview and publishing. For a project using https://example.com, the destination becomes https://example.com/contact. Prefer a full URL when adding an important destination, and check the project’s website address. Expansion does not run when that address is missing or invalid. Links already using full addresses, email or phone schemes, and same-page anchors are not changed by this expansion step. A path such as contact, without the opening slash, is not the same as /contact.

Published posts feed back into the list

After publishing, theStacc attempts to reconcile the list with published posts that have a recorded live URL. This can make those posts available to later articles and avoids adding a URL already recorded. The update is best effort. A successful publication does not prove that the list was updated, and a post without a recorded URL is skipped until that information is available. If a published guide is missing from Your Website Pages, check its actual address and add the destination manually if needed. The setting defaults to on. Turning it off instructs generation to omit internal-link references and hides Your Website Pages. It does not rewrite articles already generated or remove links from your live website. When the generation context contains no existing blog candidates, it instructs the writer to omit these references. The presence of saved pages or an enabled toggle does not prove that a particular article will contain a link. Before publishing, check the selected destinations, anchor text and any unresolved references. When a linked page moves or disappears, review both the saved entry and older articles that still point to it.
  • Preferences: manage generation settings and the list of website pages.
  • Publishing: understand publishing modes and integration delivery.