If a reader clicks your book link and sees “The requested URL was not found on this server,” they’ve reached a page that the web server can’t find at that address. For authors, the broken link might be on a book landing page, in a newsletter, or in an old social post—not necessarily on Amazon. Here’s how to trace the problem and repair it without sending readers in circles.
What “The requested URL was not found on this server” means
This message usually accompanies an HTTP 404 status. In plain terms, the server responded, but it has no page available at the requested URL. The website itself may still be working perfectly; just one address is wrong, outdated, or no longer connected to a page.
For example, your current book page might be example.com/books/garden-journal, while an old email still points to example.com/garden-journal-book. If the old address hasn’t been redirected, a visitor may get a 404.
A 404 doesn’t automatically mean that your book has been removed from Amazon or that your website has been hacked. It also doesn’t always mean the page is permanently gone. A typo, a changed URL, a deleted page, or a website configuration issue can all produce the same message.
Why book links break on an author website
Authors often share a book link in several places: their website, email signature, newsletter archive, social profiles, reader group, and promotional materials. Over time, a small change to one URL can leave older links pointing nowhere.
Common causes include:
- A changed page address. You renamed a book page, changed its slug, or reorganized your site.
- A mistyped link. A missing character, extra punctuation, or incorrect capitalization can matter on some web servers.
- A deleted or unpublished page. The page may have been removed, set to private, or left in draft status.
- A link copied from a temporary preview. A preview or editing URL may work for you while logged in but not for readers.
- A broken redirect. An old address may redirect to another address that is itself incorrect or unavailable.
- A website migration or platform change. Moving your site can change the paths to pages, even if the domain name stays the same.
There can also be a server-side problem, especially if many pages on your site suddenly return 404s. But start by checking the individual URL before assuming the entire site is down.
Diagnose “The requested URL was not found on this server”
Use this short process to find out whether the issue is the link, the page, or the website configuration.
1. Test the exact address as a reader would
Copy the link from the place where it was shared and paste it into a private or incognito browser window. This helps rule out a page that is visible only while you’re logged in to your site. Check the full address, including everything after the domain name.
Look for accidental spaces, a period or comma included at the end, an incomplete URL, or a misspelled page name. If the link is in a newsletter or social post, test that actual published link—not just the address you intended to use.
2. Check the current page on your site
Open your website’s page list and search for the book title or landing-page name. Confirm that the page exists, is published, and has the URL you expect. If you recently edited its address, the old link may no longer work.
If your site has a search function, use it to find the page. You can also visit the homepage and follow the navigation to the book. If the page is reachable through the site but not through the shared link, the shared URL is likely outdated or malformed.
3. Compare the domain and path
Check whether the working and broken addresses use the same domain and path. These small differences can point to the source:
- www.example.com versus example.com: your site may not handle both versions consistently.
- http versus https: older links may use an unsecured address that is not configured to redirect.
- A missing folder or changed slug: the page may have moved to a new location.
- A trailing slash: some site configurations treat addresses with and without a final slash differently.
Don’t change several settings at once. First identify one old address and the correct destination, then test a single repair.
4. Test other pages on the website
Open a few unrelated pages, such as your homepage, about page, and another book page. If they load normally, the problem is probably limited to one URL. If many pages fail, or if even the homepage is unavailable, contact your hosting provider or website platform before making a batch of changes.
You can also ask someone who isn’t logged in to test the address on another device or network. That helps distinguish a public problem from a browser cache or account-specific view.
Fix the link and preserve the old address when possible
The right fix depends on whether the page moved, was removed, or never existed at that URL. If you simply shared the wrong address, correct the link wherever you control it. If the page moved, set up a redirect from the old URL to the new one.
Use a redirect for a moved book page
A permanent redirect—commonly called a 301 redirect—sends visitors from the old address to the replacement. It’s useful when you’ve changed a page slug or moved your website and want old bookmarks and shared links to keep working. Many website platforms offer redirects in their settings or through a redirect tool. If you’re unsure which option your host supports, ask its support team rather than editing server files blindly.
Redirect to the closest relevant page. If a book landing page has moved, direct readers to its new location, not automatically to your homepage. A homepage redirect may technically prevent the 404, but it leaves visitors wondering whether they found the right book.
Restore or replace a deleted page
If the page was removed by mistake, restore it or publish a replacement at the original address. If you intentionally retired it, create a useful destination: for example, an updated page for a revised edition or a related book. Avoid sending readers to a page that makes claims about a book that is no longer available.
Repair the links you control
A redirect is helpful, but it’s still worth updating the original link in your website navigation, newsletter templates, social profiles, and any active promotions. Fixing those sources reduces extra hops and makes future link checks simpler.
For a book launch, keep one verified destination for the book page and copy it into your promotional materials. If you use a universal book link or a landing-page service, test its destination too; the link may load successfully while its onward link is broken.
Check your book links before a launch
A simple link audit can catch a broken page before a reader reports it. Use this checklist whenever you publish a new book page, change your site, or start a campaign:
- Open every book link in a private browser window.
- Test the link on a phone as well as a computer.
- Click through from the actual places readers will find it, such as your author bio or newsletter.
- Confirm that the destination shows the correct title, edition, and purchase options.
- Check links after changing a page slug, site platform, or domain settings.
- Keep a simple list of important book-page URLs and their current destinations.
- Ask a trusted reader or colleague to test the launch page before you send a large mailing.
If you manage several titles, a spreadsheet can make this routine easier. Include the book title, official landing-page address, store link, and the places where each link appears. Update the sheet when a page changes so old promotional copy is easier to find.
When to contact your host or website platform
Contact support if the correct page is published but still returns a 404, if redirects behave differently than expected, or if multiple unrelated URLs began failing at the same time. Share the exact broken address, the page you expect it to reach, when the problem started, and whether other pages work. Avoid sending passwords or account recovery codes.
If the failing address is an Amazon product page rather than your own website, check the link in a fresh browser and confirm that you copied the intended marketplace URL. Your website host can investigate your site, but it cannot repair an Amazon listing. Similarly, a printed link in a book requires a different response: you may not be able to change copies already in readers’ hands, so confirm the destination before approving future print files.
BookBudLC helps authors prepare print-ready interior and cover files and accompanying metadata for their own KDP accounts. It doesn’t host an author website or manage external links, so include website link testing as a separate step in your publishing checklist.
Conclusion: fix the destination, not just the error message
When “The requested URL was not found on this server” appears on your author website, first test the exact address, confirm whether the page still exists, and compare it with the current URL. Update a mistyped link, restore or replace a missing page, or redirect an address that has moved. Then check the links in your active promotions so readers can reach the right book page.
A quick audit before a launch—and after any website changes—can keep an old link from becoming a dead end. Treat “The requested URL was not found on this server” as a clue about one destination, then trace that destination back to the link readers are actually using.
