Here's a breakdown of the guidelines for publisher logo size in article schema markup for non-AMP pages, especially considering your logo's dimensions:

• Google's General Guidelines:
  • Google's general schema documentation (https://developers.google.com/search/docs/appearance/structured-data/article) doesn't explicitly prescribe pixel dimensions for publisher logos on non-AMP pages.
  • However, it emphasizes that logos should be clear, recognizable, and representative of your brand.
• AMP vs. Non-AMP Logo Requirements:
  • You're correct that AMP pages have strict logo dimension requirements (specifically, a rectangle of 600x60px). This is due to the performance and layout constraints of AMP.
  • Non-AMP pages are more flexible. The 600x60px recommendation does not apply directly.
• Key Considerations for Non-AMP Logos:
  • Aspect Ratio: Maintain a reasonable aspect ratio. Very wide or very tall logos may not display well. Google's documentation hints at a 4:1 aspect ratio as ideal, however this is not enforced outside of AMP.
  • Scalability: Ensure your logo scales well across different devices (desktops, tablets, phones). Using an SVG format is highly recommended. If using a raster format (like PNG or JPG), ensure it is high resolution.
  • File Size: Keep the file size relatively small to avoid slowing down page load times. Optimize your images.
  • Clarity: The logo must be easily recognizable even when displayed at smaller sizes.
• Using Your 1000x258px Logo:
  • Your logo (1000x258px) has an aspect ratio of approximately 3.88:1. This is close to the recommended 4:1 ratio.
  • Recommendation: You can likely use this logo directly in your schema markup for non-AMP pages. However, consider these points:
    • Test: Use Google's Rich Results Test (https://search.google.com/test/rich-results) to preview how your logo appears in search results. This is crucial.
    • Optimization: Ensure the image file is properly optimized for web use to minimize file size without sacrificing quality.
• Schema Markup Example (Snippet):

  Here's an example of how the logo might be included within your Article schema:

  
   <script type="application/ld+json">
   {
    "@context": "https://schema.org",
    "@type": "Article",
    "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "URL_OF_YOUR_ARTICLE"
    },
    "headline": "Your Article Headline",
    "image": [
    "URL_OF_PRIMARY_ARTICLE_IMAGE"
    ],
    "datePublished": "2023-10-27T12:00:00+00:00",
    "dateModified": "2023-10-27T13:00:00+00:00",
    "author": {
    "@type": "Person",
    "name": "Author's Name"
    },
    "publisher": {
    "@type": "Organization",
    "name": "Your Publisher Name",
    "logo": {
    "@type": "ImageObject",
    "url": "URL_OF_YOUR_LOGO_IMAGE",
    "width": 1000,
    "height": 258
    }
    },
    "description": "A brief summary of your article."
   }
   </script>
   

  Replace the placeholder URLs and values with your actual data. Notice the width and height attributes within the logo section.

In Summary: While Google doesn't enforce strict pixel dimensions for non-AMP publisher logos like it does for AMP, your 1000x258px logo is likely suitable. Prioritize clarity, scalability, reasonable aspect ratio, and optimized file size. Crucially, use the Rich Results Test to confirm that your implementation displays correctly in Google Search.

Disclaimer: Google's algorithms and guidelines can change. It's always a good practice to stay updated with the latest documentation.