Jump to content
thirty bees forum

30knees

Trusted Members
  • Posts

    1,469
  • Joined

  • Last visited

  • Days Won

    42

30knees last won the day on November 3

30knees had the most liked content!

2 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

30knees's Achievements

  1. Update: I turned off the datakick Bad Bot module and Varnish. Both shouldn't impact Googlebot but it looks like one of the two measures fixed the problem.
  2. I see, thank you. I wonder what then is causing the Google issues of: 1) redirects with a 403 and 2) no desktop page available. These problems are inconsistent amongst all products.
  3. Thank you for the explanation. That means the feed is providing the correct URL, i.e. https://www.example.com/en/products/84/sample-product?combination=143 However, Google complains (at least, this is what the ad agency is saying) about the redirect that then happens to the URL with the # and is unable to index the page. I get a lot of errors saying that the page is not accessible to Googlebot. If this behaviour is standard, I don't understand how Google can be having problems because of the redirect from the URL with the ? to the one with the #. This would mean that all thirtybees/Prestashop users are having problems. Which would mean the ad agency is wrong in thinking that's the reason why Google can't index.
  4. A different question: What URL do you provide to Google, the first (like it is for me) or the second: The feed outputs variant URLs such as: https://www.example.com/en/products/84/sample-product?combination=143 When this link is opened, the shop performs a 301 redirect to: https://www.example.com/en/products/84/sample-product#/72-size-large
  5. Is anybody else also suffering from this unable to view store on desktop issue? https://support.google.com/merchants/answer/12158123?hl=en I’m using a module to send product URLs to Google Merchant Center (Datakick). The feed outputs variant URLs such as: https://www.example.com/en/products/84/sample-product?combination=143 When this link is opened, the shop performs a 301 redirect to: https://www.example.com/en/products/84/sample-product#/72-size-large This means the query parameter ?combination=143 is replaced by a hash fragment. I don't know whether this is the problem or whether it's something else.
  6. Ich würde über einen Drittdienst gehen, d.h. Shop irgendwo anbinden und die leiten dann alles an DHL weiter.
  7. I am forgetful. See here: It does indeed only affect products without reviews.
  8. I am now using this one, too. The TagConcierge people never replied to my messages so I did not go with them.
  9. Thanks, but it does not help. I use Matomo and GTM together. I want to know which purchases are from Google Ads and what the cart value is. It should work out of the box with the module but something is messing that up. The data is normally taken from the confirmation page.
  10. You can update to PS8.
  11. I am using the Revws module and the Google search console says about reviews the below. Does Revws need an update to still be compliant? Missing field "itemReviewed" Items with this issue are invalid. Invalid items are not eligible for Google Search's rich results Missing field "aggregateRating" This is a non-critical issue. Items with these issues are valid, but could be presented with more features or be optimized for more relevant queries
  12. I am using Google Tag Manager. Certain events and values are not being triggered/registered in Chex. For example, the conversion value is not being sent. Is this because of Chex being different from the standard checkout and because Chex and GTM need some modifications or is it because of something else?
  13. I tried the Linea Grafica GTM module but they couldn't get it to work. Events weren't triggered. I don't see that version here: https://github.com/tagconcierge/tc-prestashop-module-free/releases Where did you get it from?
  14. Update: Die Schnittstelle thirtybees (für die Suchmaschinen: Prestashop 1.6) und Lexoffice funktioniert jetzt auch für Amazon-Rechnungen, sodass deren Inhalt (aber ohne Belegbild) nun an Lexoffice inkl. Buchungssätze übermittelt werden. Was bei Lexoffice nicht sehr gut ist: Die API ist recht beschränkt. Man kann beispielsweise Belege nicht als "bezahlt" übermitteln und "offene" Belege kann man nicht einer oder mehreren Umsätzen zuordnen. Viele Entscheidungen von Lexoffice sind unverständlich bzw. ich habe das Gefühl, dass absichtlich auf Partnerdienste verwiesen wird, statt Funktionen einzuführen. Newcomer: https://bimetrics.de/ liest sich gut aber bislang per Email unerreichbar.
×
×
  • Create New...