Avinash Kumar Sharma

Hello @kratosgemini,

Thank you for reaching out 🙂

I checked this with our development team, and we would need a bit more detail on what exactly you would like to achieve using a constant or filter.

Currently, SureMail already includes a built-in Email Simulation feature that you can enable from the dashboard:

1. Go to SureMail > Settings
2. Scroll down to Email Simulation
3. Enable the checkbox to activate it

Once enabled, emails will be simulated instead of being sent.

You can also refer to our documentation here for more details:
https://suremails.com/docs/email-simulation/

If you can share a bit more about your specific use case (for example, environment-based automation), we’ll be happy to discuss it further with the team and see how we can improve this experience.

Looking forward to your response.

Best Regards,
Avinash

Hello @stephansfp ,

Thank you for your kind words! We’re glad to hear that SureRank is adding real value to your stack and that you appreciate our focused approach.

It’s also great to know you’re happy with our support and business model. We truly appreciate your support.

Best Regards,
Avinash

Hello @seodev ,

Thank you for sharing the site URL.

I tested your URL in the Schema Markup Validator, and initially received this message:

“The URL was not found. Make sure the domain name is correct and the server is responding with a 200 status code.”

After that, I tested the page by directly pasting the HTML markup into the validator. The results show that the WebPage schema is properly added to your homepage.

The Rich Results Test does not display all schema types. It only shows structured data that is eligible for Google rich results (such as FAQ, Product, Article, etc.).

Schema types like WebPage, WebSite, and several others are valid schema types, but they are not supported as rich result enhancements, which is why they do not appear in the Rich Results Test.

This is expected behavior and does not mean the schema is incorrect.

If you want to validate whether the schema is correctly implemented (regardless of rich result eligibility), the correct tool to use is the Schema Markup Validator:
https://validator.schema.org/

For reference, Google explains which structured data types are eligible for rich results here:
https://support.google.com/webmasters/answer/9012289#enhancements&zippy=%2Cenhancements-amp-rich-results%2Cadditional-response-data

Regarding your note about missing schema on surerank.com – the Rich Results Test will only show supported types (for example, FAQ). Other valid schema types will not appear there if they are not eligible for rich results.

If you’re seeing specific errors in the validator output, please share a screenshot or the exact error message, and I’ll be happy to review it in detail.

Best Regards,
Avinash

Hello @seodev ,

Thank you for the details.

Google’s Rich Results Test currently crawls only up to around 2 MB of rendered HTML. If a page’s size exceeds that limit, Google may stop parsing before reaching the schema code, which can result in no detected items even though the schema is present.

You can read more about how Googlebot crawls and processes pages in the official documentation (last updated February 3, 2026):https://developers.google.com/search/docs/crawling-indexing/googlebot.

Also, our design team has optimized the site, and now the schema is visible in the Rich Results Test for our site.

Could you please share your site URL? We’ll test it on our end and check what might be preventing Google from detecting the schema.

Best Regards,
Avinash

Hello @noboo ,

The dev team tested the scenario with the environment you mentioned, and it is working on our end.

Further, the team would like to confirm if you are not using the Pro plugin on your site. This will help them provide a proper solution to create a table with filters.

Please raise a support ticket with us so our team can assist you more efficiently. You can contact us at: [email protected]

Best Regards,
Avinash

Hello @zlatimuud,

I tested the filter before sharing this with you, and I have recorded a short screencast to show exactly how the filter works.

Please check the screencast here and give it a try: https://share.zight.com/RBupp4K8

If the issue still persists, please feel free to raise a support ticket with us so our team can assist you more efficiently.

You can contact us at: [email protected]

Best Regards,
Avinash

Hello @zlatimuud ,

Thank you for reaching out 😊

To achieve this, you can use a small filter that adds a Reply-To header to all outgoing emails.

You can add the following code to your site via code snippets plugin.

add_filter( 'wp_mail', function( $atts ) {                                                                                                                   
      // Add reply-to header if not already present                                                                                                            
      if ( ! empty( $atts['headers'] ) ) {                                                                                                                     
          $headers = is_array( $atts['headers'] ) ? $atts['headers'] : explode( "\n", $atts['headers'] );                                                      
                                                                                                                                                               
          // Check if reply-to already exists                                                                                                                  
          $has_reply_to = false;                                                                                                                               
          foreach ( $headers as $header ) {                                                                                                                    
              if ( stripos( $header, 'reply-to' ) !== false ) {                                                                                                
                  $has_reply_to = true;                                                                                                                        
                  break;                                                                                                                                       
              }                                                                                                                                                
          }                                                                                                                                                    
                                                                                                                                                               
          if ( ! $has_reply_to ) {                                                                                                                             
              $headers[] = 'Reply-To: Your Name <[email protected]>';                                                                                        
              $atts['headers'] = $headers;                                                                                                                     
          }                                                                                                                                                    
      }                                                                                                                                                        
                                                                                                                                                               
      return $atts;                                                                                                                                            
  } );                                                                                                                                             

Best Regards,
Avinash