Welcome to the Q&A Forum
Browse the forum for helpful insights and fresh discussions about all things SEO.
CSS positions things on the page, so if you remove it, it's not surprising that lots of elements overlap. The page isn't going to look good. This is nothing to worry about.
If you want to see how a page looks to search bots, view the source of the page, don't disable the CSS.
It sounds like you need an experienced PPC manager to audit it, not PPC management software. Assuming it's a search campaign, there are a variety of things you can look at:
Find where the money is going and not converting, and plug the hole.
Bidding on other brands keywords is not illegal (although Google recently settled out of court with Rosetta Stone in a case regarding this), provided they don't use your brand name in their ad text. Sometimes it can happen with the ad text if the SEM manager isn't paying too much attention, and uploads some keywords (including your brand keywords) and is using dynamic keyword insertion in their ad text. If you're seeing your brand in their ad text, go ahead and file a complaint.
If there are competitors bidding on your brand keywords, I would take action immediately and also start bidding on them. At least in Adwords, the cost per click for your brand keywords will be much lower than your competitor is paying for them, as you should have a very high quality score for those keywords.
To be fair in your example, the Adwords click did (on average) have some effect on the ultimate sale. If the customer never came through the door looking for red widgets, they may not have purchased the blue widgets from you? There are a few different reports in Analytics that can help you see this:
I built my own Google Analytics custom reports which I export and add a few equations to in order to track ROI. I do it for a subscription site so it's not quite as complicated as it would be for an eCommerce site, where each purchase can have different items, margins, cost of goods sold, etc. What are you looking to see beyond paid search revenue to spend?
GA may be making this easier in 2013 with their "Universal Analytics" offering: http://analytics.blogspot.com/2012/10/google-analytics-summit-2013-whats-new.html.
Is it really necessary to have everything on https? What kind of information are you collecting on this lead form? Most people won't bat an eye about you collecting things like name and e-mail address on a non-secure connection, but it would depend on your customers and industry. For the visits you're getting now, are a higher percentage submitting the lead form because the pages are secure? If not, I'd flip the URLs back. https is slower and the browser won't be able to cache everything, so it makes the user suffer on every page load.
A few other thoughts (it's impossible to say without seeing your site), but having a lead form on every page may be overkill. You could just link to the form (and then have the form be secure), or you might find success collecting just the e-mail address on all of your pages, and when you collect it, have that go to a secure lead form. Then you'll have a chance to e-mail market to those who abandon the form. Something to think about and maybe A/B test.
These are duplicate pages. I'm not seeing a redirect from http://www.federalnational.com/About/tabid/82/Default.aspx to http://www.federalnational.com/about.aspx, nor is there a canonical tag telling the bot that http://www.federalnational.com/about.aspx is the canonical version.
Ideally, the platform could 301 redirect the first URL to the second. Failing that, you could place a canonical tag in the header of the page to point to the /about.aspx page.
Not relevant to the question but I also noticed in the automatically created version of the page, the active class isn't getting set on the <a>for "About" properly so it's not getting highlighted in the header.</a>
You indeed have a duplicate content problem. The PageRank for the www.telikin.com/index.php page is not contributing towards the PageRank for your www.telikin.com page. You should 301 redirect www.telikin.com/index and www.telikin.com/index.php to www.telikin.com. Personally, I don't know how to write the actual redirect, but make sure when you do it that your home page works as you could potentially create an infinite redirect when messing with your site's index page.
The trailing slashes don't matter, meaning Google knows www.telikin.com/index.php/ is the same page as www.telikin.com/index.php, so you don't have to concern yourself with that.
I think switching the two versions should be fine.
You can set up rel alternate hreflang tags if the content on your site is duplicate between English and Spanish. This will help the search engines understand that these are alternate pages based on the language, and help Spanish searches get the Spanish version of pages, and English searches get the English versions. Google talks about that here. You can do it on the page, or in your sitemap.
You can use the meta language tags or set the language in your HTTP headers for Bing to understand what's going on (see here).
It's an account level tag that works across any webpages on any domains it's included on. I've used remarketing pixels on microsites we run on separate domains, and within e-mails we send to target to those users with ads from our main site.
The URL can be counted twice and this is duplicate content. If Google sees a link to that second URL with the parameters on the end, it won't assume it's the same page as the page with the URL that doesn't have the parameters.
A few things you can do to mitigate this:
I'd be a little wary of setting rel canonical on all of my pages (I don't do this so I can't report if it works or not), so I'd personally opt for option 1 and not option 2, although theoretically each one should solve the problem.
Have you registered each of these country-specific directories of your site within Google Webmaster Tools and set their geographic target? If not, that's a good place to start. Here is Google's directions for that. Maybe that along with the rel alternate hreflang tags will be enough to clean up Google's SERPs. You don't canonical tags on any of these pages as you want each of them appearing in SERPs depending on the country of the searcher. The meta language code is more for Bing to understand what's going on (see here). Google makes more of an effort to figure out the language of each page on their own. Here is their guide on multi-regional and multilanguage sites.
Google just launched the disavow tool, and unless you've received one of those dreaded Google warnings, I'd be very wary of using it. Lots of sites have duplicate content issues or site-wide links, so it's not all that uncommon for a site to have 2,000 links to another site.
Personally, I wouldn't worry about it.
Yes, this does create a duplicate content issue. The best solution is to have /index.html 301 redirect to /. However, the canonical as you outlined above should also to fix the issue if you don't have access to your server configuration for redirects.
You can ask the webmaster of that site to correct the links so they go to valid pages on your site. Otherwise, I wouldn't bother with them. Just make sure you have a nice 404 page on your site so people who follow the links can find their way to your content without too much difficulty.
Do any pages on Domain A link to this page? Is it going to be off-putting or strange for users to get whisked off to Domain B when they follow these links? If so, is this a place where a cross-domain canonical might make more sense?
If you go the redirect route, do make sure to update all your internal links from Domain A to go directly to the page on Domain B as to not bleed any link juice by going through the redirect, and to help mitigate the surprise of changing domains (some people look at link destinations before clicking links).
The Google Webmaster set up sounds right to me!
You should set the rel alternate on all pages that go back and forth, not just the English pages. That way if Google wants to return a Thai page to an English searcher, it'll know to reference the English page. This is the set up Google recommends in their help documentation.
Don't worry about a new sitemap for the /th/ pages. Your current set up should be fine.
The article addresses this. Setting the language in the content-language meta tag will override the lang attribute in the html tag or the title tag. They're recommending to use one method to set the language and stick with it, rather than setting the language in multiple places on a page.
So, setting the lang on the tag is fine, just don't set meta content-language tags that specific a content, or set the lang in your <title>tags.</p></title>
They talked about this on the Bing Webmaster blog awhile back. You can read about it here. There is a priority order. The article states:
Keep in mind that the priority order for these tags is: , , <title>. In other words, the document location set in the “content-language” meta tag will always supersede the document location indicated in the <html> or <title> tag. Its best that you use one option, instead of multiple options here.</span></p></title>
The Bing Webmaster Central article where they discuss how to set the language for your pages is here.