diff --git a/PyBay/templates/layout.html b/PyBay/templates/layout.html
index 8ccb72b..8e7ab10 100644
--- a/PyBay/templates/layout.html
+++ b/PyBay/templates/layout.html
@@ -47,7 +47,9 @@
   <title>PyBay 2025 - 10th Annual Bay Area Python Dev Conference - {% block title %}{% endblock %}</title>
   <meta name="title" content="PyBay 2025 - 10th Annual Bay Area Python Dev Conference">
   <meta name="description" content="10th Annual Python developer conference - longest running on the US West Coast.  Join us in San Francisco!">
-
+  <meta name="author" content="Bay Area Python Association (BAPyA)">
+  <!-- published time --> <!-- most sites will parse the date correctly if we leave time blank -->
+  <meta property="article:published_time" content="2025-05-25">
   <!-- Open Graph / Facebook --> <!-- this is what Facebook and other social websites will draw on -->
   <meta name="og:type" property="og:type" content="website">
   <meta name="og:url" property="og:url" content="{{ site.get('/')|url }}">
diff --git a/README.md b/README.md
index 45dfb6f..856d37c 100644
--- a/README.md
+++ b/README.md
@@ -8,6 +8,7 @@
  - Make changes to code
  - Check for errors; check that the site displays correctly in multiple browsers and mobile.
  - Inspect with other support tools (e.g., Lighthouse, https://metatags.io/ for share cards, social metadata. etc.) make sure share cards display correctly and metadata is correct.
+ - LinkedIn Post Inspector (https://www.linkedin.com/post-inspector/inspect/) gives a more detailed view of errors, but does not work through redirects.  You can make your GitHub Codespace Public and test (same box as 'open browser' link when you first run it), and also check after changes are in production.
  - Commit and push to your branch (`git add -u`) (`git commit -m "your update descriptions here"`) and (`git push`)
  - Open PR and request review before merging with the main branch
  - After comments and requested fixes are made, merge PR to the main branch.