Jump to content

PoochKingdom

Member
  • Posts

    32
  • Joined

  • Last visited

Everything posted by PoochKingdom

  1. Your top banner is an image that's 1920x1080 that's being cropped into the site banner at 2543x440 (on my desktop screen) <div id="#banner-area-wrapper">. I looked at it using mobile mode and it shows the entire banner image. Is that an intentional design? Do you get the same layout shift warnings on mobile? If not (and I'm no expert on this), perhaps the image cropping is causing the layout shift warning - given you're taking 1080 and chopping the top and bottom of the image to get to 440?
  2. Is there a possibility that the pop-up you have for subscribing is affecting the metrics? It caused a big glitch when I visited the site and this will translate to a layout shift. I get errors about multiple H1s, and slow page load warnings from Google Lighthouse, and other tools, when I have promotional popups and cookies enabled. Since we don't have a lot of traffic to our site at night, I temporarily turn off those items and run my crawls and metrics. It has a major impact on my results. I hope this points you in the right direction.
  3. You have cast a very wide net; there are literally thousands of results. For starters, have you tried 'Feng Shui Consultants near me'? Check if your page is using keywords that will get you recognized in your local area. If not, start by concentrating on getting your SEO pages and home page driving local traffic, then go from there. Use a free browser SEO plugin like Ahrefs to allow you to see if your pages have the correct SEO titles, descriptions, and content. It is a slow and methodical process. Small steps... Edit: I just looked at your site with Ahrefs plugin, and your site title contains 'Feng Shui Consultations', not 'Feng Shui Consultants' so you need to work on keywords for sure. In addition, your home page title ('FENG SHUI CONSULTATIONS FOR GOOD FORTUNE!') ought to be h1, and yours is h2. This can have an impact on search results.
  4. We changed the page headings on our site over a month ago. It took the best part of a month for it to be reflected across all of our 50+ pages in Google, and it took more than that with Bing. In fact, some of our pages are still not indexed by Bing even now, despite us using IndexNow. You'll just have to be patient, and try submitting individual pages for re-indexing by Google.
  5. I ended up building two versions myself to embed reviews into my wife's website: The first used JavaScript with the Google Maps API and Google Places API, and I embedded this on the page using a tool called slick slider. It is a total coding solution, and the Google Places API only gives you the last five reviews. My second version uses JavaScript and a Google Cloud Function, where it uses a service account to access the Google My Business API (which I had to request separately) using OAuth2. It was a challenge to get it working, but it works well now it is in place. I am able to get all of the reviews, and can code for the future. I retrofitted this into the same slick slider for convenience sake. If you're not a coder, then one of the popular embedding solutions like Elfsight would be better for you. Depending on the popularity of your website, you can be paying between $50 and $100 per year, depending on what you would like to implement.
  6. It isn't just related products: Product list in store (alt="" + alt="<alt text of product image>") <div class="products-flex-container"> Background image (alt="" + alt="<filename of background image>") It used to affect the image in our page footer, but I replaced the standard image block with some markup code so I could control the HTML and the alt attribute. It appears to be widespread.
  7. The site audit function on Ahrefs definitely points these things out, but the plugin is nice because it's an instant audit. I also downloaded and tested my site with an application called Screaming Frog. It is yet another tool for SEO, but it's good for analyzing the types of things we're discussing: titles, headings, descriptions, metadata, etc. It requires an install. The free version is limited in functionality, but I really like it for sanity checking any changes I make to my site.
  8. I was a lead technical consultant for a software integration startup that was a low-code solution. We were asked to see if we could pull from Google's Gadget API (brand new in 2008/2009) and get/put data into SAP and Salesforce. I had to learn and implement OAuth 1.0a in our platform. It was a challenge then, and is still a challenge now for headless integration; we were an appliance-based solution. I face the same challenge today, because I'm trying to figure out how to implement the Google My Business API in our site without exposing the keys, and use it to serve up all the reviews from our Google Business listing. It requires OAuth 2.0, but I don't want any user interaction where you have to approve logins, etc. That's for another day...
  9. Agreed, though Google already has a bulk submission API that's OAuth based. I am not sure if they will adopt IndexNow, because they are pretty set in their ways; I worked with Google on early OAuth 1.0a projects in 2009, so that's their preferred method.
  10. I just tested a POST to https://api.indexnow.org and it worked with no problem. The body is JSON { "host": "<host>.com", "key": "<key>", "keyLocation": "https://<host>.com/<key>.txt", "urlList": [ "https://<host>.com/home", "https://<host>.com/about", ... "https://<host>.com/..." ] }
  11. That did it! It never occurred to me to 301 to the static page directly. You guys are awesome! Thanks!
  12. My key is loaded to /s/<key.txt>, and I have a 301 redirect from / to -> /s/, which in turn leads to https://static1.squarespace.com/static/..../<key>.txt. If I hit the URL from a browser, the key is downloaded. I have a second version of the same key loaded to /s/MyKey-<key.txt>, and I have a 301 redirect from / to -> /s/, which in turn leads to https://static1.squarespace.com/static/..../MyKey-<key>.txt. If I hit the URL from a browser, the key is downloaded. Tests and results from Postman: From Postman GET https://ssl.bing.com/indexnow?url=https://<host>.com&key=<xxx> returns HTTP 202 GET https://api.indexnow.org/indexnow?url=https://<host>.com&key=<xxx> returns HTTP 202 GET https://yandex.com/indexnow?url=https://<host>.com&key=<xxx> returns HTTP 202 GET https://ssl.bing.com/indexnow?url=https://<host>.com&key=<xxx>&keyLocation=https://<host>.com/[<key.txt>|<MyKey-<key.txt>] returns HTTP 202 GET https://api.indexnow.org/indexnow?url=https://<host>.com&key=<xxx>&keyLocation=https://<host>.com/[<key.txt>|<MyKey-<key.txt>] returns HTTP 202 GET https://yandex.com/indexnow?url=https://<host>.com&key=<xxx>&keyLocation=https://<host>.com/[<key.txt>|<MyKey-<key.txt>] returns HTTP 202 Failures GET https://ssl.bing.com/indexnow?url=https://<host>.com&key=<xxx>&keyLocation=https://static1...com/[<key.txt>|<MyKey-<key.txt>] returns HTTP 422 GET https://api.indexnow.org/indexnow?url=https://<host>.com&key=<xxx>&keyLocation=https://static1.com/[<key.txt>|<MyKey-<key.txt>] returns HTTP 422 GET https://yandex.com/indexnow?url=https://<host>.com&key=<xxx>&keyLocation=https://static1.com/[<key.txt>|<MyKey-<key.txt>] returns HTTP 422 The error is Invalid Key Location, which is to be expected as they key is not delivered from the same host as the url specified From Firefox https://ssl.bing.com/indexnow?url=https://<host>.com&key=<xxx> returns HTTP 202 https://api.indexnow.org/indexnow?url=https://<host>.com&key=<xxx> returns HTTP 202 https://yandex.com/indexnow?url=https://<host>.com&key=<xxx> returns HTTP 202 I guess I wait and see if I get verified overnight. My Bing Webmaster was verified through Google Search Console; Bing says I have nothing more to do on that front. Thanks again for your advice.
  13. Thanks for the detailed reply. I tested with Postman and just a verify with Firefox, too. I'll update you later this evening with my results.
  14. I'm very new to this SEO stuff, and I've been using the Ahrefs free Firefox plugin to check my own page structure: SEO titles, descriptions, headings, etc. I'm attaching two screenshots I took of your Home page, and About page. The Home page shows your headings are out of sequence; Ahrefs claims the first heading should be H1, and it is not the case for you. Since I am new to the SEO topic, I'm tending to believe the tooling; I don't know if the crawlers actually care about the order of the headers but the warning is there. The About page has a very long description. This is probably because you have not filled out the SEO Description in the page settings -> SEO -> SEO Title and Description. My understanding is that the description factors heavily in the indexing algorithm. If you have your old version of the site, you can go back and check how it was set up to compare how your new template has affected your page structure and SEO-related configuration withing Squarespace. I hope some of the more seasoned SEO experts weigh in for you, but I hope this helps you in small way. I would install the tool and check all of your pages; you can even sign up for the free version of the Ahrefs too and perform a site audit to gain more insights into you dilemma.
  15. I have tried this multiple times and it does not work for me. I've tried the 301 with the .txt file; I've tried a keyLocation variation. In all cases, I get a 202 response. How long does verification take normally? I want to make sure I'm not being impatient. FYI. I tried Ahrefs tool, and even they do not validate the key, despite the automatic link they provide downloading the key just fine. I can only assume that the basic rules of IndexNow apply: the key must line up with the domain it is tied to, and the Squarespace redirects ultimately lead to a https://static1.squarespace.com, not (in my case) https://poochkingdom.com.
  16. One thing to note. I have added social media share buttons to our product pages with some JavaScript. When I share to X and pre-populate the subject and URL, the card image does not always populate first time. I realized that it is most likely because X reads the raw Squarespace page looking for the "twitter:" meta tags, and the link provided by default is 1500w, and there's nothing you can do to change it. Also, most importantly, the code above may not work if X reads the raw page. This is because, in the raw page, the card is defaulted to 'summary', and will only have 'summary_large_image' after rendering. I did find, however, that either a) refreshing the X post page will sometimes pull the image, or b) you must reduce the image size by compressing it a little more. The compressed image will still be the same dimensions, but will be a smaller size. We're trying to keep our compressed images under 500Kb.
  17. I've had to fix this myself. Here's some code you can insert in the Website Tools > Code Injection > Header I've commented it as best as possible. You will replace the '***' bits with your "@username", and you need to get the URL for the image you want to use when it's needed. Squarespace seems to not set the twitter:image for regular pages, but does set it for shop items. I use my site logo by default. I'm no expert on JavaScript optimization, but this is a functional script. It is pretty efficient, so it shouldn't affect your site loading by any significant amount. It waits for the document to load, then builds a string containing the HTML that contains some comments, the twitter site, and an image if one does not exist. The twitter card can be left as 'summary' or overwritten to whatever you need ('summary_large_image'). Read the comments. The image meta element is inserted if it does not exist at all, or if it exists but the content is empty. Optionally, you can replace the image URL that has been inserted in store items by Squarespace. Be careful to comment or delete this section of code if it is not applicable. The last line of the function inserts the comment + site + image + ending comment at the end of the <head> section of your page. You can verify with a browser debugging tool. This gives you a working function that ought to be enough for you to complete your use case. Good luck! <!-- Twitter Card Summary Large by Alan Moore (webmaster@poochkingdom.com) --> <script> // Only run this script after the content has loaded // Important that this is here window.addEventListener('DOMContentLoaded', function () { // Optional comments so you can find the injected section var commentStart = '<!-- Injected by Twitter Card Summary Large -->'; var commentEnd = '<!-- End Injected by Twitter Card Summary Large -->'; // Set up the initial comment and the twitter:site value twitterMetaText = commentStart + '<meta name="twitter:site" content="*** Put your @username here ***"/>'; // Change the twitter card type if you want. Delete the line below if you're ok with it being a summary (the default) document.head.querySelector('meta[name="twitter:card"]').setAttribute('content', 'summary_large_image'); // Find the twitter image meta element var twitterMetaImage = document.head.querySelector('meta[name="twitter:image"]'); // If there's no image meta, or there is and the content is empty if(twitterMetaImage == null || (twitterMetaImage && twitterMetaImage.getAttribute('content').length == 0)) { // Insert a default image twitterMetaText += '<meta name="twitter:image" content="https://images.squarespace-cdn.com/*** Path to the image you want to display ***">'; } // Only add this section if you want to overwrite the image that's already been inserted by Squarespace // If there is already an image and you want to replace it else if(twitterMetaImage && twitterMetaImage.getAttribute('content').length > 0) { // The URL to the image can be static, or you can programmatically calculate the value // Uncomment the line below to replace the image // twitterMetaImage.setAttribute('content', 'https://images.squarespace-cdn.com/*** Path to the image you want to display ***'); } // Add the trailing comment twitterMetaText += commentEnd; // Update the document document.head.insertAdjacentHTML("beforeEnd", twitterMetaText); }); </script> <!-- End Twitter Card Summary Large -->
  18. Support said they opened a case for this. Given we're not privy to any bug tracking numbers to correlate our cases to actual fixes, I don't even believe a case was even opened. It seems the standard response is along the lines of "we notified engineering, but we can't tell you if/when it will be fixed." I won't be opening any more support cases, and I will move off Squarespace when our subscription comes up for renewal. I think it's a waste of time trying to help.
  19. FYI @Lesum, support were particularly uninterested in opening a bug for this. The support representatives (multiple) were hung up on the fact that the invalid "@media" directive was discovered using tools like W3C Jigsaw. The general sentiment appears to be, "Squarespace is a CMS, so tools like this can't be trusted to give accurate results. Consequently, we're not going to investigate or open a case." They even went as far as saying that they had no escalation path for a report like this, so they take it that engineering are not interested in having them reported 🤷‍♂️ Even including the offending CSS snippet in my emails did not convince them. I guess that reporting bugs is passé.
  20. Thanks @Lesum I'll open a bug to ensure it is tracked.
  21. I've been running a variety of site analytics tools against my site, https://poochkingdom.com, and I've noticed a lot of validations are failing on invalid CSS that's provided in the templates. I wanted to double-check the issues using the W3C Jigsaw tool, and after a bit of head scratching about parse errors, I realized that some of the CSS selectors are incorrect when it comes to media directives. Question 1: If I understand correctly, shouldn't the "@media" block be outside of the selector? Should I open a bug for this or will browsers ignore the error? .fe-block-yui_3_17_2_1_1718560167175_52219 { grid-area: 25/3/30/9; z-index: 5; @media (max-width: 767px) { } } Question 2: I've seen some CSS shared on the forums using "@media" and borrowed some for my site. Jigsaw is saying the syntax is incorrect until I add the 'only' qualifier. Is this because Jigsaw is out of date, or because this syntax is out of date? I haven't found a definitive answer online. Parse error @media screen and (max-width: 575px) .... Parse ok @media only screen and (max-width: 575px) .... Thanks in advance.
  22. I reported to Squarespace support that Bing is most likely not indexing most Squarespace pages due to invalid HTML in <img> tags - where the user has taken the time to populate the alt tags in their images. Squarespace includes two alt tags: one empty, and one populated. Bing doesn't like it, my research appears to show. Google ignores the issue; Bing does not. I have asked for a high priority fix as this probably affects a large number of Squarespace users. You can only see the offending tags when you right-click -> view page source in the browser; it does not show in the developer consoles because the DOM is already fixed after page loading. During the initial crawl by Bing and Google, they analyze the raw HTML page. Microsoft is generally more pedantic on standards, so my hypothesis is that Bing sees the invalid HTML and tags the error incorrectly. It appears as an empty alt tag warning, when actually there are two tags in the same element and this is invalid HTML. Because of this, 100% of my product pages are not indexed by Bing. I encourage you to contact support if you're still having problems with your site.
  23. I just discovered, and reported to Squarespace support, that Bing is most likely not indexing most Squarespace pages due to invalid HTML in <img> tags - where the user has taken the time to populate the alt tags in their images. Squarespace includes two alt tags: one empty, and one populated. Bing doesn't like it, my research appears to show. Google ignores the issue; Bing does not. I have asked for a high priority fix as this probably affects a large number of Squarespace users. You can only see the offending tags when you right-click -> view page source in the browser; it does not show in the developer consoles because the DOM is already fixed after page loading. During the initial crawl by Bing and Google, they analyze the raw HTML page. Microsoft is generally more pedantic on standards, so my hypothesis is that Bing sees the invalid HTML and tags the error incorrectly. It appears as an empty alt tag warning, when actually there are two tags in the same element and this is invalid HTML. Because of this, 100% of my product pages are not indexed by Bing. I encourage you to contact support if you're still having problems with your site.
×
×
  • Create New...

Squarespace Webinars

Free online sessions where you’ll learn the basics and refine your Squarespace skills.

Hire a Designer

Stand out online with the help of an experienced designer or developer.