We launch websites every month or two for clients, and make many website updates. What are the best ways to tell the “internet” that your site is up, and ready to be checked out? I’m going to focus on the free options, as I find anything that costs money sketchy (especially with regard to listing a site).
We can divide this into a few categories:
- Search Engines
- Social Networking
- Peer Sites
- News Aggregators
A growing sector in web development nowadays is the SEO “expert”.
With the blossoming effects of social networks and rapidly developing online presences, many people consider themselves SEO experts because they can gain visibility for your site.
One could argue, that’s exactly what SEO (Search Engine Optimization) is, making sure your site gets visibility.
I’m going to stay neutral on that subject, but say that SEO should generate organic traffic to your site through cooperation with modern search technologies. Proper SEO shouldn’t be a Boom and Bust scenario, but a constantly growing user base.
With all of these new SEO experts comes a group of individuals who are NOT skilled in all the fundamentals on the internet.
One warning I wanted to throw out there, is Google distorts search results for users based on sites they have clicked on previously. Take a look at Google History, and you’ll see what I mean.
Google History takes your previous browsing behavior and organizes it. That information is used to tailor your search results, and I’m sure for Google to customize their search engine performance overall.
When doing SEO you frequently search for a few search terms every day, and may click on the results you like.
SEO experts should know that the results they see may differ wildly from the rest of the world.
All SEO experts should use “neutral” browsers without Google Toolbar installed such as Firefox or Safari (yes, it’s available on the PC too — and it works pretty well) to test the search placements of their clients.
Additionally, if you have hired an SEO expert, be sure to cross reference their results with searches on indepedent computers. Your SEO expert may say your site is now “top 5” when it is in fact only in the top 20. This is because their computer is biased based on that user’s history.
This is a big win for us web developers. It helps maintain all the SEO work that has gone into a site, and lets us move site architecture around with minimal impact.
Many times I run across companies whose website just went from ASP/CFM/JSP/PHP/CGI/HTML/HTM to ASP/CFM/JSP/PHP/CGI/HTML/HTM. Fill in the blank, migrating from one platform to another is a big deal. To make matters worse, how is a search engine supposed to know NOT to link to an old file, and to redirect the same relevancy to the new file?
The magic of 301 Redirects
301 is an HTTP Status code (just like 404 and others, 403, 500, etc).
301 tells browsers and search engines that a page has been “Moved Permanently”
How can you do a 301 redirect?
First off, do NOT attempt redirecting unless you know specifically what to do. Trying to implement a meta-refresh tag will hurt you more than it will help. Search engines have become wise to the meta-refresh game that spammers have been involved with. Do not do it.
There are 2 routes to take, server side, and code side.
Server Side 301 Redirects
If you’re lucky enough to be working on a server supporting .htaccess files, your life is easy.
- Create a file called “.htaccess” in the root of your website
- Open the file in a text editor
- Set the contents to the following (replacing original, and new):
Redirect 301 /original/original.html http://www.yoursite.com/new/new.html
RedirectMatch 301 (.*)\.htm$ http://yoursite.com$1.html
- In IIS (internet services manager), right click on the old file
- Select “a redirection to a URL”
- Enter the URL for the new page
- Select “The exact URL entered above” and “A permanent redirection for this resource.”
- Click “Apply”
HttpServletRequest req1=(HttpServletRequest) request;
StringBuffer ReqUrl= req1.getRequestURL();
String RequestUrl=ReqUrl.toString();String source;
source = RequestUrl;
str = source.substring(0, source.indexOf(".jsp"));