With an average ~5 daily visitors coming in from search, I think it will be hard to be able to see any difference there to be honest, even if 1 more visitor would come in per day it would be lost in the day-to-day fluctuations.I get this is a marathon and not a sprint but I'm not seeing any differences. Installed on 1/10, most of the screenshots show a difference by this time. For reference my site has 85K posts, the 4 problem pages are related to wiki but I wouldn't think that makes a big difference.
Please let me know if there's anything I need to do differently here.
View attachment 263934View attachment 263936View attachment 263935
Went through a name change about 8 months ago and now have 2500 topics, I do see results in Google though so it's hard to say. It does act like it's being penalized/restricted for some reason but not sure how to research that.With an average ~5 daily visitors coming in from search, I think it will be hard to be able to see any difference there to be honest, even if 1 more visitor would come in per day it would be lost in the day-to-day fluctuations.
Is the domain new or recently been moved? I find it a bit weird that an established forum with 85K posts wouldn't get more traffic that that unless it has been penalized/is new/too generic/competitive niche.. How many threads are those 85K posts?
The 4 pages shouldn't be a problem no.
The 0% Good URLs I find a bit odd tho..On our own site that is at 99.8% with AMPXF
in google search console check under the Security & Manual actions.Went through a name change about 8 months ago and now have 2500 topics, I do see results in Google though so it's hard to say. It does act like it's being penalized/restricted for some reason but not sure how to research that.
Okay, done. Both say "No issues detected" and I also checked looked here so see if there's a blacklist somewhere https://mxtoolbox.com/blacklists.aspx all checks out.in google search console check under the Security & Manual actions.
Cool. What's under Core Web Vitals?"No issues detected"
HTML Event attributes, aka 'on*', are not allowed in AMP. Instead use 'amp-bind'.
on="tap:AMP.setState({ membersVisible: !membersVisible })"
Hmm interesting, could you open a support request on ampxf.com and put the link to the affected page and we'll have a look at itGoogle Search Console giving me this error.
Only reporting it on one page so far. I checked the source and the only on attributes that I can see are similar to this.
Code:on="tap:AMP.setState({ membersVisible: !membersVisible })"
Hmm interesting, could you open a support request on ampxf.com and put the link to the affected page and we'll have a look at it
Cheers
//Jonathan
Hmm, I think you have to be a bit more specific what you want to achieveHi, I'm trying to hide a specific navigation ID from the offcanvas via CSS. How do I approach this?
So I have the home button removed via css with the following code:Hmm, I think you have to be a bit more specific what you want to achieve![]()
[data-nav-id="home"] {
display: none;
}
- Bugfix where the AMP-broken url checker would hilight some
admin.php
links as "broken"
Oh okay, yeah theSo I have the home button removed via css with the following code:
I want it to be consistent on the amp pages and want that also removed from the navigation. However that doesn’t work in the amp extra.less file.Code:[data-nav-id="home"] { display: none; }
data-nav-id
-attrs are irrelevant for the AMP pages (they are used by JS in the canonical pages..)amp-state
-element there to keep track of some similar things, and it has an ID that matched the "node ID" and can be utilized with a "sibling selector" to hide the link:#homeVisible + a {
display: none;
}
.M [href="/"] {
display: none;
}
We use essential cookies to make this site work, and optional cookies to enhance your experience.