Welcome to the Q&A Forum

The method you have described is no or low risk.  The only factor I would look at is the domain authority of teh sites you are targeting to make sure it is beneficial.

Hey Aaron! Thanks for providing us with this answer, we looked into this direction and found the bug that caused the glitch in how the traffic was being redirected the wrong way. Much appreciated!

Aloha Robert! Wow great help and response!! This is hugely valuable and I will be sure to be switching up the domain and brand name with many thanks to you Robert. One more quick question concerning Garden Island, we have a newpaper and a few brands here that have Garden Island incorparated to their companies and domain's, would the specificty of www.gardenislandweddingphotographer.com or www.gardenislandweddingphoto.com (Kauai im hoping that engines would indetify or associate garden island to) be enough to have an impact/correlation for "Kauai Wedding Photographer" through engines? I will be sure to give you a shout if anything comes up, and even if everything goes smoothly I will be sure to send a smugmug link where you can download for print a few Kauai scenery photos as a very big thank you for the help! Many thanks again Robert! Aloha, Jon Gibb

Thanks for your input Aaron. Makes a lot of sense to me.

Hi Jordan,                     Thanks a lot for such useful info. Kind regards

No problem! Yes, same is true for HTTP and HTTPS

No clear answer to that question. I would review why and where google is pulling the information from.  Then try and track down the issue from there. Here is a great article on it which goes into a deep dive.  https://moz.com/blog/why-wont-google-use-my-meta-description Hope that assists.

Think of your page like the front of a newspaper. Your H1 is your big headline. Short sharp and to the point. People skim pages when reading, but will read headlines. If the H1 catches the attention they are more inclined to read on. Continue skimming down the page of the newspaper (your page) you may skip 'normal text' but your eyes catch the next H2, which is like your newspaper sub-title. I went to a Matt Bailey seminar once, and he did a great piece on how pages catch the attention and how people read/skim pages. He has a book which also covered it.

Hi Everett, Yes it seems that this is the way. Thanks a lot.

Thanks for this, Aaron. I am currently weighing both virtual confirmation pages and event tracking method. Never tried the event tracking method though. As far as my knowledge about virtual pages, they will not trigger the conversion if the attempt is failed.

A short product description on my sites is about 100 words and a unique photo with a generous caption - so about 150 words total. Most products get a much longer description of at least 300 to 500 words and at least one unique photo.  The short description described above is often upgraded after we receive a few questions about a product or after we get more experience using the product ourselves (we have experience using almost every product that we sell).  When the descriptions are improved, the rankings often go up and the page starts pulling in traffic for long tail keywords.  These are the two benefits that we see from improving product descriptions. Better selling products and those that receive lots of questions can have even longer descriptions of 500 to 1000 words and more photos.  Best selling products also usually have separate articles that explain how to select the product, how to use them, how to maintain/repair and more.  We always have links to these articles within product descriptions.  Our product pages and article pages often rank #1 and #2 in the SERPs.  We also have lots of #1, #2, #3 positions as a result of our article pages. These really long descriptions usually have the essential info in the first one or two paragraphs.  Information after that has subheading to make it easy for shoppers to scan and skip/read parts of the description that they want. If we have a product that gets a few returns we often add information about the product that caused people to return it.  We would rather kill a few sales than incur costly returns.

Since most of your searches will be city specific, I would definitely recommend having landing pages for each city. There, you can go into more detail about the specific widgets for each city and what makes them unique. It's fine to have some localized content served up on your home page, but I would recommend having some static, non-dynamic content there as well. Spend some time thinking about what the "default" version of the page would be. A good question to try to answer is: what should a user see if they're coming to the site from an IP you don't have content for, or even an IP outside of Canada? A home page is a great place to show who you are in a broader sense, and give users and search engines an idea of what you're about and why they should trust you. You can include that information along with a modicum of local-focused content that appears based on the user's IP address, that encourages them to click through to the local-specific landing page where they can get more in-depth information. I hope that helps!

You come through again, Laura! I really appreciate the links and guidance you have provided. Now, to explain this to my client -- wish me luck.  

I checked the source with my default user agent (in this case Firefox) and did NOT see an H1 tag. I checked with my user agent set to GoogleBot and DID see an H1 tag, which did have that keyword phrase in it. I checked again with a default user agent, but this time with JavaScript disabled, and could not see anything at all on the viewable page (blank white page), though the source code was there without the H1 tag. So it seems to me like you're pre-rendering the page for GoogleBot, and are including the H1 (and other header tags) as part of a fully-rendered page for search engines. However, because that Header tag does not exist if you turn JavaScript off - or if you're not Google - there may be a risk of Google seeing this page as "cloaking". Pre-rendering is good. It's not a "bad" type of cloaking if you serve the EXACT same page to search engines that you serve to everyone else. Unfortunately, this does not seem to be the case with the way this page is set up. Google sees one thing, other visitors (with or without JavaScript enabled) see something else. I know developers are head-over-heels for single-page apps and JavaScrpt frameworks, but this stuff is starting to drive me nuts. It's like trying to optimize Flash sites all over again. On the one hand you have Google bragging about how great they are at crawling JavaScript, even going so far as to say pre-rendering is not necessary... And on the other hand there are clear, sustained, organic search traffic drops whenever developers start turning flat HTML/CSS pages into these single-page JavaScript framework applications. My advice to you is that if you're going to Pre Render a page for Google, to A: make sure the page a user with JavaScript enabled sees is exactly the same as what Google sees, and B: See if you can pre-render pages for visitors without JavaScript enabled as well.