Click here to view larger image
Click here to view larger image

301 URL Redirect for AspDotNetStorefront

 E-mail this product to a friend

Maintain search engine page rankings and help customers find the right pages during site transfers or changeovers from other shopping cart platforms. Use with all file types and manage redirects with a convenient SQL database table.
No Source Code needed!
301 URL Redirect for AspDotNetStorefront - Modification installed
Price: $449.00 
   What version do I need?

Existing Pages URL Redirect for AspDotNetStorefront : Save the search engine page rankings of moved, deleted or unpublished pages in your shopping cart by redirecting traffic to a new or alternative destination. This valuable add-on works with individual products, categories or any page you need. : $449.00
Reviews (5/5)
The Right Redirect?
Our 301 URL Redirect add-on is perfect for site transfers or shopping cart system changeovers (moving to AspDotNetStorefront). For redirects to new pages on your existing AspDotNetStorefront shopping cart, try our Existing Page URL Redirect add-on.
301 URL Redirect forwards traffic from each page of your old ecommerce site or shopping cart platform to the right page on your new AspDotNetStorefront shopping cart. Preserve valuable search engine page rankings and retain site traffic by seamlessly redirecting customers to your new pages.

This add-on can create an unlimited number of redirects and works with all file types including asp, php, jsp, html, htm and aspx (302 redirect only for aspx; for aspx 301's see our Existing Pages URL Redirects). New page destinations are stored in a SQL database table for easy importing and management from your existing shopping cart admin console. The system even safeguards against missing destination pages by sending visitors to a default page on your new shopping cart site. Installation is included and we can also assist with redirect database importing.

Frequently Asked Questions
Question:We are updating a site from ASPDNSF to ASPDNSF 9.4.2. Will this work on site upgrades where the ProductIDs and SENames are changing? - Andrew (12/01/2014)
Response:Hello Andrew, if your are changing IDs and SENames, you actually need the Existing URL Redirects instead of this one. The 301 Redirects is for those people switching to the AspDotNetStorefront platform from other, but the Existing URL Redirects is for those changing URLs/IDs or removing pages etc on AspDotNetStorefront.
Question:We are having some issues getting this to work 100%. When AspDotNetStorefront configures IIS, the 301 works fine. But, if there is a page that 404's and it's not setup in the 301 settings, the PageNotFound.aspx is called (which is fine, I would rather that then redirecting to default.aspx), but it goes into a redirect loop - Alan (07/22/2014)
Response:Ok, this is due to the PageNotFound.aspx/IIS recycling the event and causing a loop! The best fix for this is to edit the PageNotFound.aspx.cs and put this directly after the Page_Load function opening tag so headers are used: Response.TrySkipIisCustomErrors = true; Response.Status = "404 Not Found"; Response.StatusCode = 404; (the first one above being most important)
Happy INDEPENDENCE DAY SALE!!! Take part with 20% off!!!
(use coupon   FIREWORKS   sitewide)
Please note all our plugins and modification now include installation!
Thank You for shopping at for you AspDotNetStorefront add-ons!