I prefer recording into an action (such as one named "Recording") that I have deleted from the Runtime Settings' Logic section. As you record, insert each identifier from your list after each action.
After the default Action section is deleted, it still appears in the list at the top of the icon list, but is shown with a grayed out icon. I do this to avoid accidentally running recorded scripts before editing, which I've done too many times because new actions are automatically added to the Logic list in Runtime Settings. Record several actions in sequence (rather recording one action, then stopping and starting with another action).
Sooner or later, you're going to wish you had a prior version of a script you're working on.
To make sure you have a version to fall back to, zip up the script folder immediately after you get a script to work.
In the "Start Recording" dialog: Parametize hard-coded URLs, user id, passwords, and other variable data by inserting in its place a new parameter such as a Date/Time stamp and entire files obtained dynamically so that the script can dynamically replace parameters to simulate use of different data during a run.
If your website uses automatic redirection, be sure to treat all Googlebots just like any other user-agent and redirect them appropriately.
If HTTP redirection is difficult to implement, you can use Java Script to redirect users to the URLs pointed to by the tag.