I'm working through some issues on semrush and they've highlighted that I've got duplicate title and meta descriptions on the following URL types:
domain-home.com/
domain-home.com.
I don't know how the second url would've come about so I'm not sure how to fix it. I can't see anything in the htaccess that would've generated that . after the domain so I'm not sure how to fix it.
Does anybody have any ideas?
Thank you
It turns out the reason was because the client had included a link to the home page in the text of one of their pages that had a full stop within the href.
This caused the issue for semrush.
Next time I'll think about whether or not the reason could be simple human error rather than some more complex reason.
Related
My website worked correctly until last week, when suddenly lots of "not found" errors appeared. The error message is visible but I cannot find the reason. The errors stated that the pages that are unable to be found are linked from sitemap.xml, however prior to the errors appearing Google was able to crawl through the website correctly. Here is an example:
Real link in sitemap (This is the old link that is still functional):
https://rohamweb.com/webdesign/174-طراحی-حرفه-ای-سایت-در-تهران.html
What the search console is actually pointing to:
https://rohamweb.com/webdesign/174-
Apparently the crawlers cannot read content after -, likely due to the different language. I have never encountered this issue until last week, in which perviously was functional.
Thanks in advance for the help!
If this is the actual link :https://rohamweb.com/webdesign/174-طراحی-حرفه-ای-سایت-در-تهران.html, you are doing it wrong and it should be URL encoded before sending it to the response:
https://rohamweb.com/webdesign/174-%D8%B7%D8%B1%D8%A7%D8%AD%DB%8C-%D8%AD%D8%B1%D9%81%D9%87-%D8%A7%DB%8C-%D8%B3%D8%A7%DB%8C%D8%AA-%D8%AF%D8%B1-%D8%AA%D9%87%D8%B1%D8%A7%D9%86.html
In this case, all of the available engines are able to follow it.
I'm trying the Branch.io API and I think I'm getting a weird problem because I'm not able to create my links properly: I can use the link for starting the app without parameter: this link http://4t3i.app.link/KDSYTMnSZs.
It works perfectly but as soon as I try to put some parameter following the doc for appending query parameters, it returns a File Not Found Webpage.
I tried:
https://4t3i.app.link/a/?&jobId=saucisse
https://4t3i.app.link/a?%24deeplink_path=article%2Fjan%2F123&%24fallback_url=https%3A%2F%2Fgoogle.com&channel=facebook&feature=affiliate&user_id=4562&name=Alex (that's the example they give)
I have the feeling I'm really missing something but no idea what. Is that so easy to add parameters: just a/ and then appending parameters??
Alex from Branch.io here:
We recently made a major back-end change to accommodate some new technical limitations that Apple imposed with iOS 9.3.1, and unfortunately it looks like we didn't fully update all our docs yet!
Your links are correct, but the /a is no longer necessary. So they would be:
https://4t3i.app.link?&jobId=saucisse
https://4t3i.app.link?%24deeplink_path=article%2Fjan%2F123&%24fallback_url=https%3A%2F%2Fgoogle.com&channel=facebook&feature=affiliate&user_id=4562&name=Alex
When you open these, you'll be able to see the link clicks coming through on this dashboard page
Thanks for noticing this. I'll make sure we get the documentation changedto reflect the new system.
Edit: also note that those examples above create new links with the specified parameters. If you simply want to append an additional parameter to an existing link, you'd do this: http://4t3i.app.link/KDSYTMnSZs?jobId=saucisse
We have never experienced this issue in Umbraco 4, but we've got this twice in Umbraco 7.
The Problem
So we've got a page: www.mywebsite.com/sale
It has been working for a month, then suddenly it shows 404:
The (non-ideal) Solution
We could change the template of this document, eg. from SalePage to TextPage, then back to SalePage.
That will temporarily fix it.
But after IIS restart, or after republishing the page, it will show the 404 error again.
For a permanent fix, we have to change the page name, eg. from Sale to Sale1.
The Question
Sometimes changing the page name is not an ideal solution at all.
Has anyone experienced this? Or know where to look? May be the database has a corrupted entry somewhere..?
We found the problem! We have this structure under Content:
Home
HomeSlide1
HomeSlide2
Pages
Sale
About Us
etc
The problem started when someone created a "home slide" under Home called "sale".
So, both Home/sale and Pages/Sale has the same path: /sale/
Deleting/renaming Home/sale fixed the problem.
This sounds like a corrupt cache.
To find out what went wrong:
Investigate the xml config (/config/umbraco.config)? I suspect this file will still contain the correct information.
If the umbraco.config file doesn't contain wrong elements, check the examine indexes. When you do a "rebuild indexes" from the developer node in the umbraco backend the problem might go away also.
If you know what is going wrong, you can start finding a solution for fixing the issue. E.g. finding out which action went wrong.
I'm hoping someone can help me because this is driving me crazy.
I have a multilingual DrupaL 7 site set up with English being the main language and French being the secondary language. I have url aliasing set up and for the most part it works correctly.
The problem arises when I have pages that I don't want included in a menu, so I leave the "provide a menu link" box unchecked. Even if the "Generate automatic URL aliases" box is checked for those pages without a menu link, the page completely ignore any url alias patterns I have set up and the url always shows up as 'node/31' instead of 'my-content-page'. If I hardcode in a URL alias via the URL path settings on the page, it WILL take those, but this is not what I want. I want it to take the url alias pattern I've set up for it. I even installed the "Pathauto persistent state" module and forced the "Generate automatic URL aliases" to remain checked just in case, but my alias patters are still ignored.
Both English and French pages do this if the page is not provided a menu link.
Has anyone seen this behaviour before? Does anyone have any ideas what might be wrong?
Thanks!
This can happen when you have tokens in your URL alias pattern that doesn't work for any reason. In your case it sounds like you have a pattern including a "menu item" token, so when you save your node without a menu item, the URL alias is not created.
The solution would be to either include a menu item, manually add your URL alias, or change anything looking like [node:menu-link] in your URL alias patterns to something else.
I think I had the same problem, and the point was that the "Basic Page" content-type needed to have available the menus of the appropiate languages in its "menu settings" (in admin/structure/ then "edit" basic-page) .
Hope this will work for you too.
If your have a non english site, follow the issue: https://drupal.org/node/1847444 and patch or solution.
I had the same problem and I solved it, "I hope forever", by reading the comment written by enzipher:
This can happen when you have tokens in your URL alias pattern that
doesn't work for any reason.
I'm using a custom pattern and I solved it by following these steps:
I went to pattern page, deleted custom token and save
I went to node and edit, then saved the node and url alias had been created like domain/language/title_node
I went to pattern page, insert same custom token and saved
I went to node again and edited it, then saved and the correct node url alias has been created
domain/language/custom_token_content/title_node
A website of mine is behaving weirdly. The layout sometimes is fine, and sometimes it is screwy. An example page that I see the problem on is this one: link
Disclaimer: I have yet to start my investigation into cause in earnest. I am turning to Stackoverflow because I am lazy and I hope someone will say "That happened to me once, it is probably this...". So please, no one get stuck into this working out this issue if it is something you have never seen before, as it wouldn't be fair as I have not done it myself.
Ok, some background:
The problem usually (maybe always) occurs when first viewing the page
The problem does not show up always, only sometimes
When the page shows up munged, if you refresh it usually reloads looking as it should
The site is a rails app
The css is passed through the neat Smurf Gem, which automatically minifies the CSS and Javascript on the page.
The layout problems happen in firefox (both linux and winXP)
The CSS is served up in the production environment using the ":cache => true" option which concatenates all the css files into one file
Anyway, I am hoping that this has happened to someone before and it will be really simple to fix. If not, I'll go and investigate and return with the solution (or a request for more help).
Thanks in advance!
James.
[edit]I added the first two bullet points, inspired by the comments and first answer[/edit]
We have had something similar when using HAML and SASS that resulted in the CSS being completely unavailable. It only happened on deploys. We determined it was a combination of the Rails stylesheet merging and the generation of the CSS from SASS. Sass was not done generating the CSS, which it did so on the first request to the application, when Rails attempted to merge it all together. The result, a corrupt useless CSS file. Then we stumbled upon this article which has a solution for preventing this issue.
Based on all this, my best guess is that the Smurf gem is attempting to generate your file on the first request, but Rails is serving it out before its done. The generation completes then each following request is fine. If this is the problem then the only solution i know of is to get the file generated before the first request. Of course, this does assume that it is related to deployments or application restarts in some way.
Peer
I had such a problem. The problem was only at the first time the page was loaded. Just reload it and it was fine.
The problem in my case was that the images where not there in the cache for the first time so the browser didnt know it's dimensions when preparing the page which caused the problem
If an image doesn't have a height/width assigned to it, a place is created on the page and it's put there. If the image doesn't quite fit, the browser may not know this until it's refreshed. Then it already knows the size and can properly fit it onto the page.