Type in your suggestion - new feature or improvement idea

SEO enhancements - 301 Redirects

As per our e-mail exchange, we'd like to request the ability to do 301 redirects. It's not something everyone will understand the value of, but it is a very good idea. It would benefit everyone, but especially those switching an existing site to a WA site.

Here are some additional details of why they are important. As per a previous email exchange from Dmitry, I'll post these comments here...

55 votes
Sign in
Sign in with: Facebook Google
Signed in as (Sign out)

We’ll send you updates on this idea

Corey Creed shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
  • Susan Branch Smith commented  ·   ·  Flag as inappropriate

    Simon, even if you have a custom domain, you still need to redirect from www to non-www or vice versa. https redirection from http is another matter.

    Wild Apricot, with all that we know of SEO these days, as Bobette says, the appearance of duplicative content is a traffic killer and our sites are being penalized for not redirecting.

    I've advised my client and will have to move to another solution if a solution doesn't appear, at least on the horizon.

  • Bobette commented  ·   ·  Flag as inappropriate

    Unfortunately, Simon's solution does not work for our site. There are still duplicate pages--both are secure. Apricot Kernel, how do we avoid duplicate content in the search engines? This is a traffic killer.

  • Simon van Lieshout commented  ·   ·  Flag as inappropriate

    To redirect all traffic to your custom domain or your www. version and avoid duplicate content penalty on search engines: use a custom domain. Ask wild apricot to install a free SSL certificate for your domain. Then change your security settings so all traffic goes via Https. Hey presto, all your traffic is redirected to your chosen domain.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Please implement this, it is extremely crucial for our website and without it we can't purchase an SSL as doing so will cause us to lose all our ranking in SERP, and losing all of the 10k back-links that we currently have

  • Scott Hendison commented  ·   ·  Flag as inappropriate

    We are considering moving two established WordPress memnbership sites onto Wild Apricot, but without 301 redirects from our old URLs to the new ones, all search rankings would be lost. Is there no method for doing so? Thet would sort of be a dealbreaker in some cases...

  • Sharon Graham commented  ·   ·  Flag as inappropriate

    [quote user="Keith Webb"]

    We also need this function. We're loosing in the search engine rankings because our search data is split between www and non-www addresses.

    There's about 8 ways to add this functionality. I hope you can add it soon!



    We also need to be able to redirect rather than having duplicate websites. This is a huge SEO issue as we lose Google rankings for duplicate sites.

  • Keith Webb commented  ·   ·  Flag as inappropriate

    We also need this function. We're loosing in the search engine rankings because our search data is split between www and non-www addresses.

    There's about 8 ways to add this functionality. I hope you can add it soon!


  • Dmitry Buterin commented  ·   ·  Flag as inappropriate

    Sorry, it will likely be a while before we address 301 redirects so if this critical for your site, you are better off using a different service.

  • ooyoi.com commented  ·   ·  Flag as inappropriate

    I don't just want a 301 redirect from a www/non-www domain but I need this. As search engine will see my website as two webistes and therefor will have duplicate content. Google will frown on the duplicate content. This is an issue I need to have resolved A.S.A.P. as I need great ranking in order to be seen in indexing.

    This needs to go to the top of the list of things that need to be done. This should be a mjor problem for every Website owner.

    I really like working with WildApricot and would hate for a 301 redirect to be the reason I look for a new service.

  • Gary C commented  ·   ·  Flag as inappropriate

    Here's how I would love to see this implemented..

    Custom Resource Not Found Page

    Add a new functional page named, "Resource Not Found." Only one of these would be allowed. We can edit the content of the body, and optionally use a token to display the resource url to in the body. The page would be displayed with the full site chrome (menu, header, footer, and such) as any other page. This way, if a visitor is displayed an RNF, they will be more likely to stay on the site.


    Add a new sub menu to the Web pages menu in the admin view named, "Redirections." Display a grid of paths and the page that each path should redirect to. The system should detect requests to one of these paths and send a permanent redirect to the path of the mapped page. Multiple redirection paths could be associated with any page, providing a lot more flexibility.

    In general, I'd love to see a lot more grid edit support. Needing to individually open each page to edit things like title and description is very time consuming.

    Resource Not Found Log

    Add another sub menu to the Web pages menu named, "RNF Log". Each time the custom RNF page is displayed (as described above), add the time, resource path, and referrer to a log file (XML?). This tab would show the log in a grid. We could see the individual requests, but also view the grouped values (individual paths & counts, individual referrers & counts). The referrers would help us reach out to others to fix links when viable.

    For any given resource path, we could use the interface to easily map it to a page going forward, which would be added to the Redirections tab.

    There would be buttons to clear and export the log.

← Previous 1

Feedback and Knowledge Base