Hi. I have recently paid for some SEO work and one thing that was reccommended to be done was redirecting some URL's.
I was told I need to redirect the following 3 versions to the main homepage:
http://www.youngandmoodie.com.au/index.php
http://youngandmoodie.com.au/
http://youngandmoodie.com.au/index.php
Could someone please give me the exact info I need to place in the htaccess. I've read a few conflicting things on this and don't want to mess it up. Thanks very much
Craig.
I love how some of these companies charge you all this money and they can't take 5 minutes or less to do this for their customer. It's not rocket science and I think they should. I do.Yam wrote:Hi. I have recently paid for some SEO work and one thing that was reccommended to be done was redirecting some URL's.
I was told I need to redirect the following 3 versions to the main homepage:
http://www.youngandmoodie.com.au/index.php
http://youngandmoodie.com.au/
http://youngandmoodie.com.au/index.php
Could someone please give me the exact info I need to place in the htaccess. I've read a few conflicting things on this and don't want to mess it up. Thanks very much
Craig.
DL
This account is inactive. Look for us under the name 'EvolveWebHosting' and contact us under that username.
Thanks!
Hi. The home page address is
http://www.youngandmoodie.com.au/
I have a vqmod called "beop all clean url's" installed. This doesn't matter does it?
Thanks for the advice.
Cheers, Craig.
http://www.youngandmoodie.com.au/
I have a vqmod called "beop all clean url's" installed. This doesn't matter does it?
Thanks for the advice.
Cheers, Craig.
The little girl in yellow seems unconvinced.
The 'beop all clean urls" should not matter.
The primary landing address is http://www.youngandmoodie.com.au/ but is that what they apparently wanted everything to point to (I assume so, hope so)?
You listed http://www.youngandmoodie.com.au/index.php (ending in a file) and both youngandmoodie.com.au/ (no file) and youngandmoodie.com.au/index.php (ending in a file) -- not http://www.youngandmoodie.com.au/ (no file and at the moment the primary landing). That being their list, the file/nofile differences raise an uncertainty.
The 'beop all clean urls" should not matter.
The primary landing address is http://www.youngandmoodie.com.au/ but is that what they apparently wanted everything to point to (I assume so, hope so)?
You listed http://www.youngandmoodie.com.au/index.php (ending in a file) and both youngandmoodie.com.au/ (no file) and youngandmoodie.com.au/index.php (ending in a file) -- not http://www.youngandmoodie.com.au/ (no file and at the moment the primary landing). That being their list, the file/nofile differences raise an uncertainty.
Thanks for your replies Butte. But I'm not sure I understand your last message. Are you saying I don't need to redirect one of these? Excuse my lack of knowledge in this area. I'm just taking instruction from this SEO company. What do you think needs to be done?
Thanks, Craig.
Thanks, Craig.
The ideal target, I believe, is www.youngandmoodie.com.au/, which would mean ensuring that youngandmoodie.com.au/ (no www.) redirects to it (www.).
So long as what comes after the .com.au/ is an "index." file, which kind of "index." file it is should not matter. There is a sequence of indices taken in a default sequence (.html, .htm, .php, certain others) unless a specific one is specified (in .htaccess or otherwise). That apparently they specified index.php raised an uncertainty, because it should not matter.
What does your .htaccess file say right now, near the top, near where rewrite engine is on and the /directory/ location of OC are specified?
So long as what comes after the .com.au/ is an "index." file, which kind of "index." file it is should not matter. There is a sequence of indices taken in a default sequence (.html, .htm, .php, certain others) unless a specific one is specified (in .htaccess or otherwise). That apparently they specified index.php raised an uncertainty, because it should not matter.
What does your .htaccess file say right now, near the top, near where rewrite engine is on and the /directory/ location of OC are specified?
# SEO URL Settings
RewriteEngine On
# If your opencart installation does not run on the main web folder make sure you folder it does run in ie. / becomes /shop/
RewriteBase /
RewriteRule ^sitemap.xml$ index.php?route=feed/google_sitemap [L]
RewriteRule ^googlebase.xml$ index.php?route=feed/google_base [L]
RewriteRule ^download/(.*) /index.php?route=error/not_found [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !.*\.(ico|gif|jpg|jpeg|png|js|css)
RewriteRule ^([^?]*) index.php?_route_=$1 [L,QSA]
There's the extra info above and below this. Is that what you need to see though?
RewriteEngine On
# If your opencart installation does not run on the main web folder make sure you folder it does run in ie. / becomes /shop/
RewriteBase /
RewriteRule ^sitemap.xml$ index.php?route=feed/google_sitemap [L]
RewriteRule ^googlebase.xml$ index.php?route=feed/google_base [L]
RewriteRule ^download/(.*) /index.php?route=error/not_found [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !.*\.(ico|gif|jpg|jpeg|png|js|css)
RewriteRule ^([^?]*) index.php?_route_=$1 [L,QSA]
There's the extra info above and below this. Is that what you need to see though?
RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L]
DL
RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L]
DL
This account is inactive. Look for us under the name 'EvolveWebHosting' and contact us under that username.
Thanks!
See what it does with this, from the top . . .
Options +FollowSymlinks
Options -Indexes
<FilesMatch "\.(tpl|ini|log)">
Order deny,allow
Deny from all
</FilesMatch>
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^([^?]*) index.php?_route_=$1 [L,QSA]
RewriteRule ^sitemap.xml$ index.php?route=feed/google_sitemap [L]
RewriteRule ^googlebase.xml$ index.php?route=feed/google_base [L]
RewriteRule ^download/(.*) /index.php?route=error/not_found [L]
Options +FollowSymlinks
Options -Indexes
<FilesMatch "\.(tpl|ini|log)">
Order deny,allow
Deny from all
</FilesMatch>
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^([^?]*) index.php?_route_=$1 [L,QSA]
RewriteRule ^sitemap.xml$ index.php?route=feed/google_sitemap [L]
RewriteRule ^googlebase.xml$ index.php?route=feed/google_base [L]
RewriteRule ^download/(.*) /index.php?route=error/not_found [L]
Yes A lot of what is in that original file is inactive. If you see the # before any lines, that's ignored. It's there for some servers that need it but it doesn't apply to all of them. Plug in the code butte gave you and test it out.Yam wrote:Hi guys. Thanks for the help. Is just those few lines of rewrite I need to add then?
The other text all remains the same?
You may need to put a # before the OptionSymLinks line depending on your hosting setup.
DL
This account is inactive. Look for us under the name 'EvolveWebHosting' and contact us under that username.
Thanks!
Basically, yeah. From the top, with the #commentedoutlines stripped for brevity, that's the guts of protecting the directories' contents and certain types of files from being seen, redirecting to http://www., and setting up seo, in a preferred sequence. Stuff below that (given the snippet of yours) is apparently the rest of the original htaccess.txt file.
Where he said "# before the OptionSymLinks line depending" that will also be for any line that throws 500 (internal server error, meaning server confused). IF .htaccess sets up something in conflict with Apache or php directives, extensions, or modules, then 500 will probably be thrown.
The # comments out a line in .htaccess and other .ht* files. In other contexts in other sorts of files or code, you will see #, //, /*...*/, <!--...// -->, and others, whose point is to comment out what they precede or bracket. They shouldn't be nested, that breaks the effect. Even inside those, changing php's ? in order to silence it may still be necessary (<@php echo isn't saying anything).
The # comments out a line in .htaccess and other .ht* files. In other contexts in other sorts of files or code, you will see #, //, /*...*/, <!--...// -->, and others, whose point is to comment out what they precede or bracket. They shouldn't be nested, that breaks the effect. Even inside those, changing php's ? in order to silence it may still be necessary (<@php echo isn't saying anything).
"[How] test it, . . . know its working . . . or if . . . 500 errors . . . [and] within OC or webmaster?"
Put .htaccess as modified into play, and let 'er rip, ride your 'roo. You can address your browser to non-www and to www and should see that it winds up in www either way. If you do not comment out a line in .htaccess and it throws a 500, THEN comment it out. You will very plainly see in the address bar and at the bottom left in the status bar whether you are looking at youngandmoodie.com.au/ or www.youngandmoodie.com.au/, and if it throws 500 you will see that number in big type staring out from the screen at you. If it does not throw 500 right of the bat, it will not throw 500 later (unless you interject something else to confuse the server). There is nothing to see or do within OC (e.g., admin) or within G. anything.
Put .htaccess as modified into play, and let 'er rip, ride your 'roo. You can address your browser to non-www and to www and should see that it winds up in www either way. If you do not comment out a line in .htaccess and it throws a 500, THEN comment it out. You will very plainly see in the address bar and at the bottom left in the status bar whether you are looking at youngandmoodie.com.au/ or www.youngandmoodie.com.au/, and if it throws 500 you will see that number in big type staring out from the screen at you. If it does not throw 500 right of the bat, it will not throw 500 later (unless you interject something else to confuse the server). There is nothing to see or do within OC (e.g., admin) or within G. anything.
Not sure if you'll see this Butte. I have just realised my wholesale.youngandmoodie.com.au subdomain is not opening. I'm assuming its since we changed the htaccess. Do you know what I need to do for this subdomain to work as well as the current redirects?
Thanks, Craig.
Thanks, Craig.
Hey. Thanks for getting back. I had asked my hosting provider as well and this was the last reply. Disregard the incorrect spelling of Moodie.
OK assuming you actually want the site to load as http://www.wholesale.youngandmoody.com.au (and this isn’t a mistake) then you need to configure the DNS records. Login to your account on our website, click on My Domains and then select view details next to youngandmoody.com.au Scroll down and click DNS Management button.
Add a new line at the bottom in the 3 blank boxes as follows;
Host name = www.wholesale.youngandmoodie.com.au, record type = Address, Address = 203.63.79.90
Be sure you follow the pattern as per the other address records listed above it. Click save changes. This should allow people to find the site as http://www.wholesale.youngandmoodie.com.au if that is what you wish to do.
Once saved the changes should take around 60 minutes, after that test the url and see if it works.
Kind Regards,
Chris
----------------------------------------------
Ticket ID: #400265
Subject: wholesale site not opening
Status: Answered
Ticket URL: https://www.cheaperdomains.com.au/viewt ... c=XiWPNg0l
----------------------------------------------
Does that seem like all I need to do then Butte? The htaccess only had those additional lines added as suggested in our last posts. I'll have to go in and check the DNS but again are doing all this on my ph. I'll post back later if it all pans out. Thanks, Craig.
OK assuming you actually want the site to load as http://www.wholesale.youngandmoody.com.au (and this isn’t a mistake) then you need to configure the DNS records. Login to your account on our website, click on My Domains and then select view details next to youngandmoody.com.au Scroll down and click DNS Management button.
Add a new line at the bottom in the 3 blank boxes as follows;
Host name = www.wholesale.youngandmoodie.com.au, record type = Address, Address = 203.63.79.90
Be sure you follow the pattern as per the other address records listed above it. Click save changes. This should allow people to find the site as http://www.wholesale.youngandmoodie.com.au if that is what you wish to do.
Once saved the changes should take around 60 minutes, after that test the url and see if it works.
Kind Regards,
Chris
----------------------------------------------
Ticket ID: #400265
Subject: wholesale site not opening
Status: Answered
Ticket URL: https://www.cheaperdomains.com.au/viewt ... c=XiWPNg0l
----------------------------------------------
Does that seem like all I need to do then Butte? The htaccess only had those additional lines added as suggested in our last posts. I'll have to go in and check the DNS but again are doing all this on my ph. I'll post back later if it all pans out. Thanks, Craig.
You evidently have registrar and webhost with the same outfit, he gave you what is normal for dns A, point to the machine address, where the webhost (half of the same outfit) will send it on to the right directory. The nameserver, webserver, and mailserver machines will occupy probably several large rooms; you'll be on one or more hard drives inside one of each kind of machine or machine rack. There are several kinds of "dns records"--A is for website, there will also be MX for mail if you set up mail just for the subdomain.
In your account you will (probably also) need to "host" your own subdomain (add it to hosted domains/subdomains). That will typically launch a directory just for it, live inside about 10-60 minutes (depends upon host and timing, you may hit it just right and start seeing it within 60 seconds) while the in-house nameservers update records.
From the moment of setting the dns A record, propagation of the record among nameservers world-wide begins, completes typically within 12-24 hours regionally, 24-48 hours continentally, 48-72 hours globally. Meanwhile, traffic goes circuitously among nameservers, you and visitors might not consistently see it till namservers serving your region/continent are all updated. After 72 hours the planet is yours.
In your account you will (probably also) need to "host" your own subdomain (add it to hosted domains/subdomains). That will typically launch a directory just for it, live inside about 10-60 minutes (depends upon host and timing, you may hit it just right and start seeing it within 60 seconds) while the in-house nameservers update records.
From the moment of setting the dns A record, propagation of the record among nameservers world-wide begins, completes typically within 12-24 hours regionally, 24-48 hours continentally, 48-72 hours globally. Meanwhile, traffic goes circuitously among nameservers, you and visitors might not consistently see it till namservers serving your region/continent are all updated. After 72 hours the planet is yours.
Who is online
Users browsing this forum: No registered users and 10 guests
