Disallow, canonical, or noindex for a coupon ID parameter where Google has already found some duplicate content?
We’ve changed our software and domain a week ago. Done the 301 redirction successfully. However, we’re still facing a lot of problems, bugs, things we didn’t think about and more…
Our website is a coupon/campaign publishing website. The URL structure is domain/page?coupon_id=[NUMBER]. The “coupon_id” query adds a small piece of content to page. But rest of the page stays same.
We forgot to insert “CouponId” query as a disallow rule to robots.txt at the beginning. Even though pages have got canonical tag (weird), Google indexed these pages with CouponId query.
When we figured out this mistake, we updated disallow rules on robots.txt ASAP. Added the rule for
CouponId query as a disallow. Checked canonical , it exists for pages. But Google crawled some these pages before we do it.
- Adding Disallow rule for
CouponIdquery on robots.txt didn’t change results yet. So, This caused a big problem on SERP ranking. Should I worry about this or will waiting solve the problem eventually?
- What if we keep the canonical tag and use “no index,follow” tag while/when the URL has coupon_id query? Because basically when we add a new coupon, there will be a new content but it’ll show the page duplicated.
RE: Extended WPF Toolkit Modify 'available colors' from color picker By Alferats - on July 10, 2017
В текущем варианте свойство с таким именем ищется в объекте DataContext листбокса (и далее вверх по иерархии).Чтобы свойство искалось в...