301 redirect without using .htaccess

Hello,

I have a site lunched in may. The site was have arround 12k pages(products). So i use a addon and i create seo url for all products. After 2 month i was belive is better to change that format of link for each product.

Now google tell me i have 12k pages not found. Today i write on webmastehelp and ppl from there tell me to do a 301 redirect for all that links.

Let`s say i can identify each link for what product was( i mean by id to create a separate db). How can i do the redirect without using .htaccess because if i will write 12k rows in .htaccess will be very very big and is not ok.

Is any solution that can i do with opencart without modify to much on him?

Thanks in advance,
Andrei

Remove your add-on for SEO and leave the URL's as they are set in opencart's "default package: they will work out fine for SEO the way they are.

Blnukem wrote:Remove your add-on for SEO and leave the URL's as they are set in opencart's "default package: they will work out fine for SEO the way they are.

You know if i do this now i will have more "damage" to my site. This is not a solution.

I fact is any way to add header with 301 redirect to a page ?

and i now when i write this i think i have a solution.............i have to check it....

you can use php to add a header for 301

i find my solution and is working very well. But i don`t know if to use it or not.

I not so sure is very good ideea to have 13k of 301 redirects....just because of google....is still try to read and read and read about this thinks.

Is not many info about this thinks.......
I belive is not logical solution......every i team i change a links or something like this i have to make a 301 redirect.
with 2-3 mistakes like this and i must have like 100k of 301 redirects....
I don`t know.............google prefer to have 1 milion of links where just 10% are real link, 90% are 301 redirect....this i understande from what i read and i don`t belive this is ok.

If anyone have another tip.......

Thanks in advance for any help.....i have lost 2 days(almost 36 hours) to read about this

The simplest and cleanest "direct" traffic direction is dns A, for each domain and subdomain, to a particular machine where a particular directory awaits it, according to the "hosted" domains and subdomains in your own webserver account. Nameservers send traffic there. You can minimize additional fiddling by streamlining dns A. For each domain or subdomain your registrar dns "zone" settings will include *., http://www., subdomainname., pointing to your quad-decimal machine address -- where your list of 'hosted" domains and subdomains is set up with directories where they reside on the disc. That is the basedir/ where looping, if that occurs, recurs. (If you like the often preposterously unnecessary looping and the likewise often preposterously excessive bandwidth supporting it, then go for it -- within whatever traffic limitations your own account might have.) Just deal with your dns A settings and your "hosted" list; less than 36 hours to say the least.

Ideally, when dns A records are properly preset and hosting is properly preset, you should not need to "redirect" much of anything except to combine names on one landing, such as .net and .com or various subdomains., so that whatever people browse will go to one landing spot and plop there. That can be established so that the address bar (and status bar) does or does not show more than one name (always www. and .net, for example). Changes in dns A records take time to propagate among nameservers but are clean in their own way. Changes in redirection on the disc where traffic is diddybopping through an account tree are effective immediately but are relatively messy in their own way. You can do the latter (local, short term) in order to assess your traffic options when you set the former for keeps (dns A, long term).

You'll have to decide which means you do or don't want to use, but there are several ways to land traffic where you want it to land. There are registrar settings (dns A rather than CNAME, and alternative stealth and non-stealth forwarding) and there are webserver settings (redirects), whether in separate accounts with separate companies (registrar, webhost) or in separate sections of one account (one host). You can set the dns A (or alternative forwarding) to go to a specific machine (or instead directory). The dns A directs to the machine, your webhost then sends it to the right directory according to how many domains and subdomains you "host" in your own account. If it has a domain name or a subdomain name, you will ordinarily "host" it and list it as hosted in your webhost account. Both of those are initiated with dns A settings (for your "zone" -- there will be a *., http://www., subdomainname.). The "first subdomain" is http://www., a basic given.

You can write .htaccess itself. You can set dns A with registrar and on the webhost rely upon your own .htaccess or use the control panel's Advanced or similar settings to redirect or forward (whichever they happen to call it) a specific domain or subdomain from the nominal host(ed) directory to another one. That will ordinarily be written into .htaccess or another sort of .ht* file. Some .ht* files will not work in concert with .htaccess itself, .htaccess can do their jobs along with its own.

butte wrote:The simplest and cleanest "direct" traffic direction is dns A, for each domain and subdomain, to a particular machine where a particular directory awaits it, according to the "hosted" domains and subdomains in your own webserver account. Nameservers send traffic there. You can minimize additional fiddling by streamlining dns A. For each domain or subdomain your registrar dns "zone" settings will include *., http://www., subdomainname., pointing to your quad-decimal machine address -- where your list of 'hosted" domains and subdomains is set up with directories where they reside on the disc. That is the basedir/ where looping, if that occurs, recurs. (If you like the often preposterously unnecessary looping and the likewise often preposterously excessive bandwidth supporting it, then go for it -- within whatever traffic limitations your own account might have.) Just deal with your dns A settings and your "hosted" list; less than 36 hours to say the least.

Ideally, when dns A records are properly preset and hosting is properly preset, you should not need to "redirect" much of anything except to combine names on one landing, such as .net and .com or various subdomains., so that whatever people browse will go to one landing spot and plop there. That can be established so that the address bar (and status bar) does or does not show more than one name (always www. and .net, for example). Changes in dns A records take time to propagate among nameservers but are clean in their own way. Changes in redirection on the disc where traffic is diddybopping through an account tree are effective immediately but are relatively messy in their own way. You can do the latter (local, short term) in order to assess your traffic options when you set the former for keeps (dns A, long term).

You'll have to decide which means you do or don't want to use, but there are several ways to land traffic where you want it to land. There are registrar settings (dns A rather than CNAME, and alternative stealth and non-stealth forwarding) and there are webserver settings (redirects), whether in separate accounts with separate companies (registrar, webhost) or in separate sections of one account (one host). You can set the dns A (or alternative forwarding) to go to a specific machine (or instead directory). The dns A directs to the machine, your webhost then sends it to the right directory according to how many domains and subdomains you "host" in your own account. If it has a domain name or a subdomain name, you will ordinarily "host" it and list it as hosted in your webhost account. Both of those are initiated with dns A settings (for your "zone" -- there will be a *., http://www., subdomainname.). The "first subdomain" is http://www., a basic given.

You can write .htaccess itself. You can set dns A with registrar and on the webhost rely upon your own .htaccess or use the control panel's Advanced or similar settings to redirect or forward (whichever they happen to call it) a specific domain or subdomain from the nominal host(ed) directory to another one. That will ordinarily be written into .htaccess or another sort of .ht* file. Some .ht* files will not work in concert with .htaccess itself, .htaccess can do their jobs along with its own.

Sorry, but i don`t get your point. I know how thinks works in this domain(i have almost 15 year of network of configure routers, linux and etc).


My question is not anymore about how to do it. I have my solution and is working very good. I am not moving from from a domain to another domain or from a subdomain to another subdomain.

My question is: on www.example.com you have 12k links. After 2 mounths you change the format of that links (for example from www.example.com/alfa ->to-> www.example.com/alfa.html).
So, you will have new 12k link on domain www.example.com but google will tell you cannot find anymore fist 12k links(before make the change).

So in this situation what you do?! Do you implement a 301 redirect for old links to new links?!(because google want this?)

A 301 is traffic redirection, of traffic to one domain, subdomain, or directory, to instead another one, and it is in concert with dns A as well as .htaccess and local disc arrangements, it has nothing to do with moving or changing your domain (in your instance -- obviously, it also arises when one does that), with routers, or with operating systems. If your solution is working very well, then what is the question, why is there a question? Traffic; direction; redirection.

As Blnukem already suggested, just use just what is built into OC:
http://forum.opencart.com/viewtopic.php?f=10&t=80716
http://docs.opencart.com/display/opencart/SEO+keywords

I belive, because i change my question in topic confuse users. I should open new topic with new question.

Sorry for confusion.

Have a nice day and thanks all for answers

You do not need extensions. Google came up with 12,000 or more problems and you lost at least two days, over an approach to SEO that is palpably and obviously not working. At least two of us are not kidding, ask the extension author or bail out.

SEO built into OC
http://forum.opencart.com/viewtopic.php?f=10&t=80716
http://docs.opencart.com/display/opencart/SEO+keywords

See also http://forum.opencart.com/viewtopic.php?t=27538 as to multiple stores, just for reference.