Options for a maintenance/seo/accessible site?

[bulevardi]

I have a few questions about making a website.

Normally, I make one page with navigation and content sections.
The navigation changes the content.
For hosting, I use PHP includes to get the content changed.
Seo and maintenance friendly.
BUT: client needs to have PHP support, page reloads totally


But when my client doesn't have good hosting, without server side scripting support like PHP, and doesn't want it, what do you do than?

- you make one page with nav/content, and the content in an iFrame
(not seo friendly)

- you make one page with nav/content, and the content changes with Ajax, the page doesn't have to reload totally.
(not seo friendly too) > <noscript> tag is the only solution?

- you make every content-page with it's navigation built in
(not maintenance friendly)


Which other posibilities do we have in this situation?

Thanks

[Dan Schulz]

I hate to say it, but this sounds like the perfect situation to use Dreamweaver (code view and the find/replace features, of course).

[FaridHadi]

I'd say it depends on the site.
If it's just a small simple site your best option is to probably create all the static html pages. Without server side scripts I don't see how you have any other sensible option.
If it's a bigger site you should try to convince the client, explaining how it's better, to get a better host.

[bulevardi]

Okay, I see.

And which one of these two is the best (like in seo friendlyness).

- you make one page with nav/content, and the content in an iFrame
(not seo friendly)

- you make one page with nav/content, and the content changes with Ajax, the page doesn't have to reload totally.
(not seo friendly too) > <noscript> tag is the only solution?


I guess the last one? It avoids frames, and pages should load faster?

[FaridHadi]

None of them are SEO-friendly but if these are your only two options, I would go with an AJAX solution. If you are OK with a <noscript> solution, which means you'll have to hard code the content in it, you might as well skip that and place the content of the first page in a div tag and then use AJAX to update it's content for the other pages. This way at least the content of the first page can get crawled and indexed. This, obviously, means that the content of the first page will have to be updated in the HTML file, and the content of the other pages will have to be stored, and updated, in XML files.