Feat: seo improvements

[Alessandro100]

closes: #752

Summary:

Most impactful SEO changes listed below and why

Header Elements Very important to have h1 tags on each page, it lets google (and other search engines) know what the main focus of the page is

Page title / description Distinct page titles help determine what the content of the page is. This helps a lot of unique pages like feed details. Learned that most search engines only check the first 60 characters and after that it gets cut off. It's important to start with the unique elements of the page and end with - Mobility Database which is less unique to the feed page. Used sites like: Airbnb, Etsy, transitfeeds as reference

Table anchors Big change. Our table didn't have a tags so google couldn't crawl our feed pages. By turning the table rows into a tags, google knows to visit these pages and index them. This forced to re-think how the + 2 transit providers work. We are also pushing the boundaries of using a table element and should be revisited in the future. Now the table is more accessible and can be tabbed through

Whats next? This PR implemented the low effort / high reward SEO elements but there are a few more things that could have high impact but more effort

1. Change the feed detail url from /feeds/mdb-310 to /feeds/capital-transit/mdb-310 for better seo indexing
2. Improve the lighthouse performance on the feeds / feed page
3. Back link the mobilitydatabase.org website from our blog / website / social media content. More websites that point to the mobilitydatabse == better authority == better search ranking

Expected behavior:

Explain and/or show screenshots for how you expect the pull request to work in your testing (in case other devices exhibit different behavior).

Testing tips:

Go through the application and make sure everything looks good. Play with the feeds table. Functionality of the application shouldn't change

Please make sure these boxes are checked before submitting your pull request - thanks!

• [ ] Run the unit tests with ./scripts/api-tests.sh to make sure you didn't break anything
• [ ] Add or update any needed documentation to the repo
• [X] Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
• [X] Linked all relevant issues
• [ ] Include screenshot(s) showing how this pull request works and fixes the issue(s)

+2 is now a tool tip

Feeds Performance (NOTE: localhost kills a little performance, should be around 67)

Feed Performance

[github-actions[bot]]

Preview Firebase Hosting URL: https://mobility-feeds-dev--pr-803-jxvxzzo8.web.app