Account created on 6 February 2012, about 13 years ago
#

Merge Requests

Recent comments

๐Ÿ‡บ๐Ÿ‡ธUnited States _doyle_

Taking a look through the issue and the current state of the recipe in Drupal CMS here is what I think we should aim to change to reduce confusion and improve the user experience:

## General: Fix the issue with items not being automatically checked for items that are handled by the SEO Recipes and/or Core.
Configure XML Sitemap
Setup Cron
Enable Clean URLs
Configure Easy Breadcrumbs
Configure Honeypot
Adjust Performance Settings
Configure Image Styles

We should be able to check the things that the SEO recipe configures, but we wonโ€™t have much control over the other ones and we donโ€™t want to make this a dependency for them so some of this will need to be on the users to handle manually which I think is fine.

Additional recommendations to further improve the UX/clean up some legacy items:

## Search Engines
Simple Sitemap and XML Sitemap are both heavily used modules. There are use cases for both - but for Drupal CMS Simple Sitemap makes more sense. It likely makes sense from an SEO Checklist perspective to support both.
Install and Enable XML Sitemap Module should be reworded to reference/link to both.
This could be turned into a smart option checking if either module is installed and wording appropriately.
Configure XML Sitemap module should be contextual based on which module is installed.
Set Up Cron - Add a link to Drupalโ€™s Cron page w/ a longer description that we recommend this be set up on your hosting environment for more complex sites?
Group the Google and Microsoft account information together.

## Optimizing Content
On the optimizing content section - adding a 2nd sitemap is going to be confusing for new users. Recommend
Move search 404 to Clean URLs section
Consider consolidating Optimizing Content and On-page Optimization.

## On-Page optimization
Consider removing the Yoast SEO setup if the module is having issues until they are resolved - not urgent but could be a poor user experience.
Consider adding sections around accessibility with https://www.drupal.org/project/editoria11y โ†’ . Accessibility does have an impact on SEO and is included with Drupal CMS.

## Security and Performance
Remove advagg related checklist items
Reword "Secure your website with https" to "Confirm your site is served over HTTPS"
Remove Move to fast hosting.

## Mobile and Social
Change โ€œMake sure website is responsive.โ€ to โ€œConfirm your website loads responsively on mobile and tablet devicesโ€

๐Ÿ‡บ๐Ÿ‡ธUnited States _doyle_

Thanks for the feedback! Let me remove the path_alias collection from the request.

From a user point of view, especially users coming from other CMS's having insight into Pathauto patterns is really important. They work differently in other CMS's and Drupal actually has a lot of power. Exposing the initially configured Drupal CMS patterns would be very useful contextual information for this dashboard, but I fully understand the size constraints. I don't think the full functionality should be there as you, we can link back to the main URL to manage them.

What do you think about an informational block for Automated URL Patterns.
1. Title: Automated URL Patterns
2. Description: Automated Path Settings provide a powerful way to control the structure of URLs across your Drupal site, ensuring they are both user-friendly and optimized for search engines. This feature automatically generates URL aliases based on customizable patterns, reducing the manual effort required to manage URLs and helping to maintain consistency across the site.
3. Pattern Name | Pattern | Type
4. Add a CTA link at the bottom to "Configure Your URL Patterns"

This gives content editors/site builders the understand that this is here, its easy to use and configure without having to "know".

๐Ÿ‡บ๐Ÿ‡ธUnited States _doyle_

_doyle_ โ†’ created an issue.

Production build 0.71.5 2024