Tag Info

New answers tagged

0

Another way to do it: /content/ -- current content with no redirect /content/content-2013 -- last years content Then when 2015 rolls around, you move the contents of /content/ to /content/2014 and put the 2015 content in the place where it used to be. If people are linking into 2013, you don't get the direct benefit of their links this year, but that ...


1

The simplest method would be: # Redirect to HTTP 404 File/Page Not Found Redirect 404 "/ja/any_posts" Redirect 404 "/ja/all_posts" Redirect 404 "/fr/any_posts" Redirect 404 "/fr/all_posts" Though you could also use: # Redirect to HTTP 404 File/Page Not Found RewriteRule ^ja/any_posts$ - [R=404,L] RewriteRule ^ja/all_posts$ - [R=404,L] RewriteRule ...


0

Something along these lines might do what you want. This will redirect the user to the 'main' version of the page, and add a 404 header in the process, removing the old link: RewriteCond %{REQUEST_URI} ^/(ja|fr)/ RewriteRule ^(ja|fr)/(.*?) /$2 [L, R=404]


1

Your challenge will be whether you have internal teams (or old visitors) that will be unhappy about seeing new content if you redirect and archive. We were doing this with great success, but the fact that the FB open graph objects locked in with the older meta and like counts really challenged our analytics. We had to discontinue doing this but it ...


1

Is it smart to redirect 301 old content 2013 --> 2014 and make a new archive page? Or keep it like this? I would keep it like this because users would be unhappy to see their link pointing to something new without warning. Now, if link juice is your concern, there would be nothing wrong with putting an internal link from older years pages to current ...


0

Well, how that page can hurt your SEO process if that do not exist in web? Right. hen you have made a proper redirect from blog page to domain, then there should not be any issue of duplicacy even if they have same content or titles.


1

It's not strictly a DNS setting. You would have to change the settings on your web server. You will need to have the friendsmusic.com DNS A record point to the IP Address that mydomain.com/friend is hosted at. Then assuming you are using an Apache web server you can go into the configuration file example: /etc/apache2/apache2.conf and create a mod_rewrite ...


1

The only solution I can think of here is a server alias. A server alias points to your domain name on web server level. It can send the user somewhere without the URL changing But you must note: the domain should be hosted at your hosting company you should redirect all links to example.php/. Note the /, otherwise the real URL will be shown. It's a ...


0

You could look into doing a "frame redirect". It is also sometimes called "web forwarding" or "masked redirect". In that case the redirect server issues content like this: <html> <frameset rows="100%,*" border="0"> <frame src="http://www.example.com/my-page.html" noresize frameborder="0"> </frameset> </html> This causes ...


0

Without having to specify a domain in the circumstance that multiple domains point to the website root or that a production .htaccess rules can be applied to: RewriteCond %{HTTP_HOST} ^(.*)\.ANYdomain\.com [NC]


1

I think your question is a bit confusing, probably mainly because you have some terminology mixed up. A redirect literally just means that a client tried to load a certain URL, and the server redirected them to another page. Whether or not this is the page the user intended has little to do with it from a technical standpoint. A HTTP Status code is a ...


0

Google Analytics uses a JavaScript snippet to do all the tracking. No JavaScript runs on redirect requests. That means that Google Analytics can't track redirects directly. There are two approaches I use for this type of tracking: Campaigns If these redirects are tracking clicks from other sites, then you probably want to use Google Analytics campaign ...


0

Try this: #gateway.school.edu virtual host RewriteCond %{REMOTE_ADDR} ^10\.(.*)$ [OR] RewriteCond %{REMOTE_ADDR} ^172\.(.*)$ [OR] RewriteCond %{REMOTE_ADDR} ^192\.(.*)$ RewriteRule .* reset.school.edu [R=301,L] The .* is a wildcard. The \ escapes the . which anchors the match allowing it to be taken literally. The () may not be necessary- it is usually ...


1

The appropriate way to do this is to use the the rel=canonical attribute on your page. This will identify one source URL for your content. For example: <link rel="canonical" href="http://blog.example.com/dresses/green-dresses-are-awesome" /> Google acknowledges this issue in a write up found here: ...


4

From an SEO standpoint, moving from a keyword domain to a company branded domain is a good move. The 2014 SearchMetrics Ranking Factors found that that having keywords in the domain name is no longer a significant ranking factor. I consider hyphens in domain names to be bad for rankings as well. Moving to company branded domain name is a good move for ...


0

Short Answer is no. The answer provided by @zigojack will work. Thing is, is it worth going through all the trouble? In-Page analytics is there for convenience and at times can be misleading. You have a wealth of information inside your GA account so I would just use that.


0

Try plain old Redirect instead. Its behavior is to set up the one to one match you are looking for. The following redirects every page on your current domain to the corresponding page on your new domain. Redirect 301 / http://newdomain.com/



Top 50 recent answers are included