Welcome to the Q&A Forum

If your PPC pages use a part of the content that's already on the SEO page (duplicated content) I would noindex those pages. Trying to get both pages indexed can only backfire. A other quick indication, if those pages are only attainable through your Ads and offer no new information to users who started there visit on the home page I would also noindex them.

If however, your PPC pages offer unique value to your visitors they can't find on other pages on your website (or on your organic landingpages) you could let them get indexed.

For point 2: Having a useful internal link structure is a best practice for SEO. If your pages offer unique value I would add them (in a logical way) to your internal navigation structure. If however they **do not ** offer unique value those links won't be useful for your visitors and will only be there to support your SEO. In this case it won't do you any good.

For point 3: Your building a triangle. It doesn't make sense to try to give your PPC pages any status through internal links and then giving a canonincal to merge any status with your organic pages. Either way, I would not canonical those pages. Give them noindex or treat them like a normal page.

Since this question is pretty old, I would love to know how you handled the situation!

Hi Swendt,

Personally I would stick to what fits your overall branding strategy best. this means I wouldn't change anything about how your business name is displayed just because it's in the meta description. A few things I would consider when making this decision:

1. Is your business name merged or separated in your logo?

2. If your a existing brand, do people search for your brandname merged or separated? This gives you more insight in your customers perspective. (you can check this through Google Keyword Planner in Adwords)

3. If your business name tells potential customers something about what you do I would definitly consider readability aswell. If your business name contains two worlds I would, in most cases, separate them.

Also, I'm not a huge fan of TM aswell, but I'm from Europe so I'm not sure if it's more common in other parts of the world.

Good Luck!

Dear Felicity,

From what I'm seeing on https://www.ryanyoungdesign.com.au the 443 port isn't configured correctly. This is the standard HTTPS port. There are either two options:

1. The 443 port is set up, but is requesting the wrong files.

2. The 443 port isn't configured at all and picks up the first files it finds.

Either way you will have to ask your webdevelopment company to fix this and make sure they set up the 443 port to process the right files.

Hope this helps!